Which versions of keroeltop are malicious?

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

How do I remediate keroeltop if I installed it?

Remove keroeltop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

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

Search your lockfiles and build artifacts for keroeltop (version 99.99.99).

Malicious package

keroeltopnpm

Advisory published Sep 18, 2026Updated Sep 21, 2026

keroeltop is a confirmed malicious npm package (MAL-2026-16297) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in keroeltop (npm)

MAL-2026-16297

Immediate action

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

npm uninstall keroeltop

What this malware does

[email protected] is a lure package whose index.js runs on every npm lifecycle phase (preinstall/install/postinstall/prepare) and issues an HTTP request to the hardcoded endpoint https://eo8f3m3ho26a0nm.m.pipedream.net/<packages>?h=<hostname>, transmitting the installer's os.hostname() to an attacker-controlled Pipedream webhook. The version number 99.99.99 is the canonical dependency-confusion resolution-winning shape used to override an internal package name. The package additionally declares a dependency on requests@^0.3.0 (an npm name resembling request) and requires it at the top of index.js, causing whatever bytes resolve for that name to be fetched and loaded transitively at install time. No legitimate functionality is present.

The OpenSSF Package Analysis project identified 'keroeltop' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

89aae084914d96e7e7620a79371083c4e1bb4a838fac1633aff257c5a380eab8

0c1791fee7ca80cf7d21f57837b64f0c31594194a2733fa7a94eda87e9235199

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for keroeltop (version 99.99.99).
If you installed it — respond
Remove keroeltop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If keroeltop 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. keroeltop 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-020240

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks keroeltop-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database