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

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

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

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

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

Yes — @klapp-kyc/routes is associated with the IN-MAL-2026-005083, IN-MAL-2026-005082, IN-MAL-2026-005151, IN-MAL-2026-005150 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-kyc/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-kyc/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-kyc/routes across your stack and pipelines.

Malicious package

@klapp-kyc/routesnpm

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

MAL-2026-5412

Immediate action

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

npm uninstall @klapp-kyc/routes

What this malware does

On npm install, the package's preinstall hook executes node index.js, which collects the installer's hostname, OS username, current working directory, __dirname, and package name, then exfiltrates them through two channels unconditionally: (1) a hex-encoded DNS A-record query to a subdomain of d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live (an interactsh-style out-of-band collector), and (2) an HTTP POST of a JSON payload to http://172.201.213.59:9090/c. The package has no other functionality — package.json declares description: "security research", version 99.0.0 (dependency-confusion-style high version), and a KYC-themed scope (@klapp-kyc/routes) suggesting targeted reconnaissance against a specific organization's internal namespace. Regardless of the self-description, installers' internal host identifiers are leaked to attacker-controlled infrastructure.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

117301b4ebab6f5a18c2b3dafaa501e36c8b666a2c926950805f169ae3a982a4

ad94c92fd5b9921bc74eebca1ec5a25c4547ca62c54d9026850535d2f4c39849

47cc2d1136216fc706d2aab88cd6cf12099d78ebc723c090b93f1b93d62d101b

ca32e3aa7685d93e36eca726e08096bd0c5ba425172ef254fdf769cc09b46887

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-kyc/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-kyc/routes across your stack and pipelines.
If you installed it — respond
@klapp-kyc/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-kyc/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-kyc/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-kyc/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-005083IN-MAL-2026-005082IN-MAL-2026-005151IN-MAL-2026-005150

References

Credits

Amazon Inspector · finder

Detect & block this

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