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

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

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

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

Malicious package

efhthrthrthregerhtnpm

efhthrthrthregerht is a confirmed malicious npm package (MAL-2026-16436) that steals credentials and exfiltrates sensitive data (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

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for efhthrthrthregerht (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging efhthrthrthregerht across your stack and pipelines.
If you installed it — respond
efhthrthrthregerht 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 efhthrthrthregerht 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 efhthrthrthregerht 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. 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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database