Which versions of kongstrong are malicious?

The following PyPI versions of kongstrong are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate kongstrong if I installed it?

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

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

Yes — kongstrong is associated with the RLMA-2024-08446, 2024-07-strongkong, RLUA-2026-00456 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 kongstrong 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 kongstrong (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kongstrong across your stack and pipelines.

Malicious package

kongstrongPyPI

Malicious code in kongstrong (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10039

Immediate action

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

pip uninstall kongstrong

What this malware does

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-07-strongkong

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

76ee4c55614f3424ef150cb4923ec599704b000105c67118406ea8a59f628174

026c042543685546ac8af01459bffe8a71f710a886d8edfae5165121f8d480fc

6bc1ea7b99d0e9a3368a66084641ad782b9070c75c5ad2b67026cdd569ae344d

810d35fec918010d936d169be0d6987cb60415411149b450d639b691fdd9c53c

767d280d2ac438b3617190c999aebb3ded809e7796bc479b7568486934122ccf

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

Campaign

RLMA-2024-084462024-07-strongkongRLUA-2026-00456

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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