path-addon-extend
Node.js path module
This report shows the evidence for path-addon-extend@1.0.10. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiConfirmed import-time remote-code execution is concrete malicious behavior, not a path-module feature. No install hook is needed because normal package use activates the payload.
Decision evidence
public snapshot- `path.js` imports Node `https` at module load.
- `path.js` performs `https.get` when the package is imported.
- `path.js` Base64-decodes a Googleusercontent download URL.
- `path.js` parses the remote response then executes `eval(data.content)`.
- The remote fetch/eval is unrelated to the claimed path-module functionality.
- `package.json` declares no lifecycle scripts.
- Most of `path.js` is a copy of Node's path implementation.
Source & flagged code
3 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
path.jsView on unpkg · L574Package source references a known benign dynamic code generation pattern.
path.jsView on unpkg · L582Package declares a runtime dependency whose name matches a Node built-in module.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to path-addon-extend@1.0.10.
The versions list below shows the verdict for each recorded version.
- Avoid installing path-addon-extend@1.0.10. 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.