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

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

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

Remove @klapp-sca/routes 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @klapp-sca/routes part of a known attack campaign?

Yes — @klapp-sca/routes is associated with the IN-MAL-2026-005077, IN-MAL-2026-005076, IN-MAL-2026-005155, IN-MAL-2026-005154 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @klapp-sca/routes in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @klapp-sca/routes and packages like it before any post-install script runs.

Malicious package

@klapp-sca/routesnpm

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

MAL-2026-5417

Immediate action

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

npm uninstall @klapp-sca/routes

What this malware does

package.json declares "preinstall": "node index.js || true", so on every npm install the bundled index.js runs automatically and collects os.hostname(), os.userInfo().username, __dirname, and process.cwd() into a JSON payload. The payload is hex-encoded into DNS labels and resolved against *.d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live (an Interactsh/Burp-Collaborator-style out-of-band DNS sink) and simultaneously POSTed to a hardcoded bare IP at http://172.201.213.59:9090/c. This is a classic install-time reconnaissance beacon: installer machine identity is leaked to attacker-controlled infrastructure without any consent or user action beyond installing the package. The package's stated 'security research' description does not change the impact — any installer that runs npm install has their hostname, username, and working-directory paths sent to third-party endpoints.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

11ae6419c673fc32db76632ea472b0a5c4fdb0beff999d5e6cd8fc144abab562

495f510483f297a56d545e8555db20eb54569f904bfd71853e54a18d89812cb0

813b153ed59f9a72a56179d192cc44c350ee849ae13b02e6dd7ef36496fd9843

d896040967e9bedf9f3146daf8c14a5669d1cdb47b776a9b747d940be79c3c1e

Frequently asked questions

No. @klapp-sca/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-005077IN-MAL-2026-005076IN-MAL-2026-005155IN-MAL-2026-005154

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection