Which versions of et_phone_home are malicious?

The following npm versions of et_phone_home are flagged malicious: 0.0.5. Treat any of these as compromised.

How do I remediate et_phone_home if I installed it?

et_phone_home establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed et_phone_home — how do I know if it already compromised me?

If et_phone_home 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.

How do I find et_phone_home across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for et_phone_home (version 0.0.5).

Malicious package

et_phone_homenpm

Advisory published Nov 2, 2026Updated Nov 4, 2026

et_phone_home is a confirmed malicious npm package (MAL-2026-18607) that opens a backdoor for remote access (malicious version 0.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in et_phone_home (npm)

MAL-2026-18607

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall et_phone_home

What this malware does

Runs on install. The postinstall script fetches a path from a bare IPv4 address with wget, contacting a remote host from every machine that installs the package. Version examined: 0.0.5; tarball SHA-256 58f9b4c9c26abe6ac52353ce1e0a824fba06c8aa7cefa94d2d4805306053e82c.

Malicious versions

1 flagged

0.0.5

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for et_phone_home (version 0.0.5).
If you installed it — respond
et_phone_home establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If et_phone_home 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

No. et_phone_home on npm has been identified as a malicious package (version 0.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oluwatosin Amokeodo · finder

Detect & block this

O3 blocks et_phone_home-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database