Which versions of joyboyw are malicious?

The following PyPI versions of joyboyw are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate joyboyw if I installed it?

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

If joyboyw was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is joyboyw part of a known attack campaign?

Yes — joyboyw is associated with the 2025-11-joyboyw 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 joyboyw across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for joyboyw (2 malicious versions).

Malicious package

joyboywPyPI

Advisory published Dec 5, 2025Updated Dec 31, 2025

joyboyw is a confirmed malicious PyPI package (MAL-2025-192322) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in joyboyw (PyPI)

MAL-2025-192322

Immediate action

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

pip uninstall joyboyw

What this malware does

Contains a function to silently download malware

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

Campaign: 2025-11-joyboyw

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
malware

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

36ac711534f46e41704c145912a7a6c3a51f64bb1888469e0730768e00865242

55fd309408cb22eb138ed25c51659ba48d2f1e4ebbb519e653e023d46798572a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for joyboyw (2 malicious versions).
If you installed it — respond
joyboyw 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 joyboyw was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. joyboyw on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-joyboyw

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database