registry / Data exfiltration / forge-extended
forge-extended
This report shows the evidence for forge-extended@1.0.1. 2 of 3 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 directly confirms unconsented install-time collection and exfiltration of local system data. This is concrete malicious behavior, not merely a suspicious primitive.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm installation (preinstall)
Impact
Leaks system identity, DNS configuration, and contents of /etc/passwd and /etc/hosts.
Mechanism
install-time host fingerprinting and file exfiltration
Attack narrative
Installing the package invokes index.js through preinstall. It reads host identity and network details plus /etc/passwd and /etc/hosts, then sends them in an HTTPS POST to a Burp Collaborator-style oastify endpoint.
AI rationale
Source directly confirms unconsented install-time collection and exfiltration of local system data. This is concrete malicious behavior, not merely a suspicious primitive.
Evidence
package.jsonindex.js/etc/passwd/etc/hosts
Network endpoints1
67bqctsh977zz60hiszvr1pbc2iu6ku9.oastify.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs `node index.js` in preinstall.
- index.js collects hostname, username, home directory, and DNS servers.
- index.js reads /etc/passwd and /etc/hosts when present.
- index.js POSTs collected data to an oastify host.
Evidence against
Behavioral surface
FilesystemNetwork
Source & flagged code
4 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node index.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgindex.jsView file
1const os = require("os");
L2: const dns = require("dns");
L3: const fs = require("fs");
L4: const https = require("https");
L5: const packageJSON = require("./package.json");
L6: const packageName = packageJSON.name;
...
L10: p: packageName, // Package name
L11: c: __dirname, // Directory where the package is installed
L12: hd: os.homedir(), // Home directory on the remote server
L13: hn: os.hostname(), // Hostname of the remote server
L14: un: os.userInfo().username, // Username on the remote server
...
L17: pjson: packageJSON, // Full package.json data
High
Host Fingerprint Exfiltration
Source collects local host identity data and sends it to an external endpoint.
index.jsView on unpkg · L1•matchType = normalized_sha256
matchedPackage = knowledge-grader@1.0.1
matchedPath = index.js
matchedIdentity = npm:a25vd2xlZGdlLWdyYWRlcg:1.0.1
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
4 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationindex.js
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to forge-extended@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing forge-extended@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.