Which versions of keroeltopkkk are malicious?

The following npm versions of keroeltopkkk are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate keroeltopkkk if I installed it?

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

If keroeltopkkk 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 keroeltopkkk part of a known attack campaign?

Yes — keroeltopkkk is associated with the IN-MAL-2026-020241 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 keroeltopkkk 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 keroeltopkkk (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging keroeltopkkk across your stack and pipelines.

Malicious package

keroeltopkkknpm

keroeltopkkk is a confirmed malicious npm package (MAL-2026-16336) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in keroeltopkkk (npm)

MAL-2026-16336

Immediate action

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

npm uninstall keroeltopkkk

What this malware does

The package ships a single server.js that is wired into every npm lifecycle hook (preinstall, install, postinstall, prepare, prepublish, preprepare, postprepare). On npm install the script reads os.hostname() and issues an HTTPS GET to the hardcoded endpoint https://eo8f3m3ho26a0nm.m.pipedream.net/, sending the installer's hostname and the package name as query parameters to an author-controlled pipedream.net webhook collector. The package has no other functionality: package.json carries an empty description, a placeholder ISC license, a name resembling a token, and version 99.99.99 — the canonical shape used to probe whether a private/internal package name resolves against the public npm registry (dependency confusion). The exfiltrated hostname discloses internal build-host or developer-machine identifiers to the beacon operator.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

2758c1a2619db534fdc8e2981e051769b20641492d12ff984e333446e0c734e3

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 keroeltopkkk (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging keroeltopkkk across your stack and pipelines.
If you installed it — respond
keroeltopkkk 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 keroeltopkkk 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 keroeltopkkk 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. keroeltopkkk on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020241

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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