Which versions of tetomood are malicious?

The following npm versions of tetomood are flagged malicious: 12.0.0. Treat any of these as compromised.

How do I remediate tetomood if I installed it?

tetomood 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 tetomood — how do I know if it already compromised me?

If tetomood was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tetomood part of a known attack campaign?

Yes — tetomood is associated with the IN-MAL-2026-020086 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tetomood (version 12.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tetomood across your stack and pipelines.

Malicious package

tetomoodnpm

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

Malicious code in tetomood (npm)

MAL-2026-16216

Immediate action

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

npm uninstall tetomood

What this malware does

package.json declares both preinstall and postinstall scripts that invoke wget to POST the installer's current working directory ($(pwd)) and machine hostname ($(hostname)) to a hardcoded Discord webhook endpoint on discord.com at install time. The tarball ships only package.json (611 bytes); the declared main entry index.js is absent, so the package has no legitimate functionality — the lifecycle beacons are its sole purpose. Installing the package causes automatic host reconnaissance data to be sent to an author-controlled remote endpoint without consent.

Malicious versions

1 flagged

12.0.0

Indicators of compromise (SHA-256)

6c09686feb7c38e815ef9a615a6ceba2444029a34ea9d6bee8598a76bc8e8f92

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tetomood (version 12.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tetomood across your stack and pipelines.
If you installed it — respond
tetomood 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 tetomood was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tetomood before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-020086

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tetomood-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