type-context
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for type-context@3.2.7. 4 of 4 known versions are blocked or flagged. The newest version, 3.2.11, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe source contains an active remote JavaScript loader, not merely suspicious dependencies or unused primitives. Absence of install hooks does not mitigate runtime remote code execution.
Decision evidence
public snapshot- `index.js` spawns detached `node lib/caller.js` when middleware is invoked.
- `lib/caller.js` fetches `https://json.extendsclass.com/bin/250fca079abb` with axios.
- `lib/caller.js` reads remote `data.cookie` as JavaScript source.
- `lib/caller.js` executes that source using `new Function.constructor("require", s)`.
- Detached child uses ignored stdio and `unref()`, reducing visibility.
- `package.json` contains no npm preinstall/install/postinstall lifecycle hook.
- No credential or local-file harvesting is present in the inspected malicious path.
Source & flagged code
2 flagged · loading sourceSource fingerprint signature matches a known malicious package signature; route for source-aware review.
index.jsView on unpkgFindings
Affected versions and remediation
This report applies to type-context@3.2.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing type-context@3.2.7. 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.