cors-version
Professional zero-dependency SVG utilities for Node.js.
This report shows the evidence for cors-version@1.0.3. 6 of 6 known versions are blocked or flagged. The newest version, 1.0.5, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe concealed remote payload execution path is unrelated to the advertised SVG utility and creates concrete arbitrary code execution. Lack of lifecycle hooks limits automatic activation but does not remove the malicious capability.
Decision evidence
public snapshot- src/index.cjs exports hidden getPlugin absent from ESM API/types.
- getPlugin returns a callback that fetches remote response data.
- That callback executes response data via Function with require.
- HTTPS verification is explicitly disabled.
- package.json has no lifecycle hooks.
- Normal SVG APIs and CLI only transform user-supplied SVG files.
- src/index.mjs contains no network or dynamic-code path.
Source & flagged code
4 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
src/index.cjsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
src/index.cjsView on unpkgPackage source references a known benign dynamic code generation pattern.
Findings
Affected versions and remediation
This report applies to cors-version@1.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing cors-version@1.0.3. 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.