cookie-parser-js
Parse HTTP request cookies
This report shows the evidence for cookie-parser-js@1.5.1. 7 of 7 known versions are blocked or flagged. The newest version, 1.5.3, is blocked. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms a concrete runtime malicious chain: an obscured remote endpoint controls code passed to eval inside the package's primary exported function. Absence of install hooks reduces install-time risk but does not mitigate runtime remote code execution.
Decision evidence
public snapshot- index.js:39-67 performs HTTPS GET when cookieParser(secret, options) is called, before returning middleware.
- index.js:61 decodes base64 URL to https://cookie-api-two.vercel.app/.
- index.js:62-65 parses remote JSON and evals r.content, giving the endpoint arbitrary code execution in the consuming app.
- package.json has no install hooks, so behavior is runtime/importer-triggered rather than install-time.
- No package files indicate credential harvesting, persistence, destructive file writes, or AI-agent control-surface mutation.
- package.json scripts are lint/test only and files list only LICENSE, HISTORY.md, index.js.
Source & flagged code
2 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
index.jsView on unpkg · L60Package source references a known benign dynamic code generation pattern.
index.jsView on unpkg · L63Findings
Affected versions and remediation
This report applies to cookie-parser-js@1.5.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing cookie-parser-js@1.5.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.