registry / Remote code execution / rollup-packages-node-polyfills
rollup-packages-node-polyfills
rollup-plugin-polyfill-node ===
This report shows the evidence for rollup-packages-node-polyfills@0.13.2. 4 of 5 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-aiThe decoded, hidden install and immediate execution of an undeclared package are concrete malicious behavior, not polyfill functionality. Absence of a lifecycle hook does not mitigate import-time execution from the published main entrypoint.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Any require/import resolving package.json main (dist/index.js).
Impact
Arbitrary code supplied by the fetched dependency can execute in the importing user's environment.
Mechanism
Obfuscated npm subprocess install followed by dynamic payload require and invocation.
Attack narrative
The CommonJS main entrypoint immediately decodes an npm-install command, spawns it silently, and after completion dynamically requires the undeclared cors-version package. If that package exposes getPlugin(), its returned function is invoked. This creates an unconsented import-time remote-code execution chain outside the declared dependency graph.
AI rationale
The decoded, hidden install and immediate execution of an undeclared package are concrete malicious behavior, not polyfill functionality. Absence of a lifecycle hook does not mitigate import-time execution from the published main entrypoint.
Evidence
package.jsondist/index.jsdist/es/index.jsnode_modules/cors-version
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- dist/index.js decodes and spawns `npm install cors-version --no-save --silent --no-audit --no-fund` on import.
- dist/index.js runs ValidateSvgModule() at module load, without user action.
- dist/index.js dynamically requires the newly installed cors-version package and calls its getPlugin()/plugin() result.
- package.json has no cors-version dependency, making the runtime install hidden and unpinned.
Evidence against
- package.json contains no npm lifecycle hook.
- dist/es/index.js contains the expected polyfill plugin implementation and lacks the injected runner.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalNetwork
HighEntropyStringsMinifiedObfuscatedProtestwareUrlStrings
Source & flagged code
9 flagged · loading sourcedist/index.jsView file
2L3: const inject = require('@rollup/plugin-inject');
L4: const modules = require('./modules.js');
Critical
Encoded Package Runner Execution
Source decodes numeric character arrays into a child-process package-runner command and executes it.
dist/index.jsView on unpkg · L2•Trigger-reachable chain: manifest.main -> dist/index.js
Reachable file contains a blocking source-risk pattern.
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg83L84: const { spawn } = require('child_process');
L85:
High
2L3: const inject = require('@rollup/plugin-inject');
L4: const modules = require('./modules.js');
Findings
2 Critical5 High5 Medium5 Low
CriticalEncoded Package Runner Executiondist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
HighSame File Env Network Executiondist/polyfills.js
HighKnown Malware Source Similaritydist/modules.js
HighKnown Malware Source Similaritydist/es/modules.js
HighKnown Malware Source Fingerprint Signaturedist/modules.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumProtestware
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to rollup-packages-node-polyfills@0.13.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing rollup-packages-node-polyfills@0.13.2. 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.