Which versions of @klapp-otp/routes are malicious?

The following npm versions of @klapp-otp/routes are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate @klapp-otp/routes if I installed it?

@klapp-otp/routes 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 @klapp-otp/routes — how do I know if it already compromised me?

If @klapp-otp/routes 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 @klapp-otp/routes part of a known attack campaign?

Yes — @klapp-otp/routes is associated with the IN-MAL-2026-005100, IN-MAL-2026-005099, IN-MAL-2026-005157, IN-MAL-2026-005156 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 @klapp-otp/routes 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 @klapp-otp/routes (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @klapp-otp/routes across your stack and pipelines.

Malicious package

@klapp-otp/routesnpm

Malicious code in @klapp-otp/routes (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5416

Immediate action

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

npm uninstall @klapp-otp/routes

What this malware does

On npm install, this package auto-executes index.js via the preinstall lifecycle hook. The script collects os.hostname(), os.userInfo(), __dirname, process.cwd(), and the package name, then exfiltrates them through two channels: (1) a hex-encoded DNS A-record query to <encoded>.d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live (an interactsh out-of-band collector), and (2) an HTTP POST of the same JSON payload to http://172.201.213.59:9090/c. Both channels fire unconditionally on install, leaking installer identity to attacker-controlled infrastructure. The package metadata reinforces the dependency-confusion / namespace-squat shape: scope @klapp-otp with version 99.0.0 and the description string security research, paired with no legitimate functionality in the tarball.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

3701ac552bd704a6c763558749e69755eadea825b90f0b0e51be120ed8bf2c01

6eebbab7c031083ae325b2262558bb759840f96f356a54ac3df3b5e1fa70ae75

8d3143a25bca88550c73189b84085b9a8770cace00d02790eb6c17520350f0bd

9246974efd1a626094dd3f2027df2e8f1468ce45ebcba42e5207a06c5c9e16ee

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

Campaign

IN-MAL-2026-005100IN-MAL-2026-005099IN-MAL-2026-005157IN-MAL-2026-005156

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @klapp-otp/routes-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