Which versions of strongkong are malicious?

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

How do I remediate strongkong if I installed it?

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

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

Yes — strongkong is associated with the RLMA-2024-09317, 2024-07-strongkong, RLUA-2026-00783 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 strongkong 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 strongkong (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 strongkong across your stack and pipelines.

Malicious package

strongkongPyPI

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

MAL-2024-10168

Immediate action

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

pip uninstall strongkong

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)

3ae5b6794434017810592438d5af4436f8cbd414ecc4d2ae1ce5c3d18ad1caca

63f2c7c1c3b7c2fdc1325b5377d3464060494763a42a63d16860b5d1e9ae98f8

c6f4a55369b1ed2f46bdac2bc627a89816b7fafe22306d285b9d2f2d5cf120b7

c30a3cbdfd24a917f5449a29960e919d7284ee4a04af47234706133df1ef8b51

7992ee07b671b26cd7ad5baed51344b3ff61670e6ff3b4d08c234b0480f93a32

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 strongkong (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 strongkong across your stack and pipelines.
If you installed it — respond
strongkong 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 strongkong 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 strongkong 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. strongkong 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-093172024-07-strongkongRLUA-2026-00783

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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