Which versions of efhthrthrthregerht are malicious?

The following npm versions of efhthrthrthregerht are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate efhthrthrthregerht if I installed it?

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

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

Is efhthrthrthregerht part of a known attack campaign?

Yes — efhthrthrthregerht is associated with the IN-MAL-2026-020322 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 efhthrthrthregerht across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for efhthrthrthregerht (version 99.9.9).

Malicious package

efhthrthrthregerhtnpm

Advisory published Sep 23, 2026Updated Sep 23, 2026

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

Malicious code in efhthrthrthregerht (npm)

MAL-2026-16436

Immediate action

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

npm uninstall efhthrthrthregerht

What this malware does

The package's postinstall hook runs index.js, which collects the installer's OS username, current working directory, hostname, and local IPv4 address and POSTs them as JSON to a hardcoded webhook.site collector URL (https://webhook.site/f9bff304-3053-4d54-be05-86537267514a) on npm install. The package name is a random keyboard-mash string with no documented purpose, and the only on-install behavior is the outbound beacon to an anonymous ephemeral webhook endpoint controlled by whoever created the webhook.site token.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

4845639223c486cf2d33751ad950cea4c7f70401877929d25c36e7d07655d820

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for efhthrthrthregerht (version 99.9.9).
If you installed it — respond
efhthrthrthregerht 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 efhthrthrthregerht 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. efhthrthrthregerht on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020322

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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