supply chain / passport

Passport.js

registrynpm
package namepassport
maintainerJared Hanson

Passport.js is the standard authentication middleware for Node.js, supporting over 500 strategies including local username/password, OAuth, and OpenID Connect. It integrates with Express and NestJS and manages user serialization into sessions. A passport strategy is invoked on every authenticated request.

api usage

Checking Passport.js

passport 0.7.0 is a clean version with no known supply chain compromise. The response returns compromised: false with an empty sources array.

bash
curl "https://api.attestd.io/v1/check?product=passport&version=0.7.0" \
  -H "Authorization: Bearer YOUR_API_KEY"
json
{
  "product": "passport",
  "version": "0.7.0",
  "supported": true,
  "risk_state": "none",
  "supply_chain": {
    "compromised": false,
    "sources": [],
    "malware_type": null,
    "description": null,
    "advisory_url": null,
    "compromised_at": null,
    "removed_at": null
  },
  "last_updated": "2026-05-01T00:00:00Z"
}
attack surface

Why this package is monitored

Authentication middleware is invoked on every protected route. A backdoored Passport version can capture session data, OAuth tokens, and deserialized user objects from every authenticated request that passes through the middleware.

Attestd monitors passport using the following detection sources:

registry

Manually curated advisories in the Attestd registry, verified by a human analyst. Confidence 1.0.

osv

OSV.dev malicious-package advisories with IDs prefixed MAL-. Confidence 0.95.

npm_deprecation

npm package versions with deprecation messages containing targeted attack language such as malicious, backdoor, or compromised. Confidence 0.80.

related