Which versions of kuaishou are malicious?

The following npm versions of kuaishou are flagged malicious: 99.9.9, 99.9.10. Treat any of these as compromised.

How do I remediate kuaishou if I installed it?

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

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

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

Malicious package

kuaishounpm

Malicious code in kuaishou (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10416

Immediate action

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

npm uninstall kuaishou

What this malware does

The package's prepare lifecycle script, which runs automatically on npm install, collects host, user, and platform identifiers along with the full process.env and POSTs them to a hardcoded ngrok tunnel at crabbing-thong-overhung.ngrok-free.dev (path /?cross_os_cloud=1). When executed in GitHub Actions, it additionally reads ACTIONS_ID_TOKEN_REQUEST_URL and ACTIONS_ID_TOKEN_REQUEST_TOKEN, requests a GitHub Actions OIDC ID token, and includes that token in the exfiltrated payload. The version number (99.9.9) and hardcoded attacker-controlled tunnel destination are consistent with a dependency-confusion / typosquat lure targeting CI environments; the OIDC token can be exchanged for cloud credentials via configured trust relationships.

Malicious versions

2 flagged

99.9.999.9.10

Indicators of compromise (SHA-256)

5b1cab5ce51f5b2683a915893076af9fd4108a2ea2cb817e8f6c275f9ef7e76c

fd1d5daf09cc7bfff164e60bf5abd0a1b374b5bb616f0a78cac8f6c6ea613608

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

Campaign

IN-MAL-2026-009806IN-MAL-2026-009805

References

Credits

Amazon Inspector · finder

Detect & block this

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