take-home-caller-idnpm
Advisory published Updated
take-home-caller-id is a confirmed malicious npm package (MAL-2026-16382) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in take-home-caller-id (npm)
What this malware does
package.json declares a preinstall hook that runs index.js on npm install. index.js collects host identifiers via os.hostname() and os.userInfo(), reads homedir, DNS server list, and cwd, and reads /etc/passwd and /etc/hosts via fs.readFileSync. The collected data is POSTed over HTTPS to the Burp Collaborator subdomain 0decr93bem6onemg3dmbydi6rxxrli97.oastify.com. The package name suggests an unrelated 'caller id' utility, but the shipped code performs only reconnaissance and exfiltration at install time; no legitimate functionality accompanies the network callback. The oastify.com destination is a Burp Collaborator out-of-band host used for exfiltration/beaconing, not a documented service endpoint of this package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for take-home-caller-id (version 1.0.1).
If you installed it — respond
take-home-caller-id is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If take-home-caller-id was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks take-home-caller-id-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.