Which versions of kotlin-stdlib-jdk8 are malicious?

The following PyPI versions of kotlin-stdlib-jdk8 are flagged malicious: 99.1.1. Treat any of these as compromised.

How do I remediate kotlin-stdlib-jdk8 if I installed it?

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

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

Yes — kotlin-stdlib-jdk8 is associated with the RLMA-2025-00479, 2024-11-0wn-sh, RLUA-2026-00457 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 kotlin-stdlib-jdk8 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 kotlin-stdlib-jdk8 (version 99.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kotlin-stdlib-jdk8 across your stack and pipelines.

Malicious package

kotlin-stdlib-jdk8PyPI

Malicious code in kotlin-stdlib-jdk8 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-939

Immediate action

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

pip uninstall kotlin-stdlib-jdk8

What this malware does

Importing the module triggers sending out the hostname to the package author. It looks to be a placeholder/pentest activity related to BytedDance.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-0wn-sh

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

99.1.1

Indicators of compromise (SHA-256)

358c5b8658e94ee68a9b8cf7816f40f6e20eddb7e39004b89adcbc04ce30b349

a64de7cff803d4506a8f4ea9b3763238a4fd70d8c429b3d4e05520837e6159d0

f217cf2fd34c9cab642b70bd9d778e6ef08a3dfba1954060a29983f2d3e6d47e

d075f478d2bda3ba78729516ff4ffa8652b844fc1f87dd489b95414f60d9c98d

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

Campaign

RLMA-2025-004792024-11-0wn-shRLUA-2026-00457

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks kotlin-stdlib-jdk8-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