Which versions of yeahmankema are malicious?

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

How do I remediate yeahmankema if I installed it?

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

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

Yes — yeahmankema is associated with the 2026-05-crayrandomiz 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 yeahmankema across my projects, lockfiles, and CI pipelines?

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

Malicious package

yeahmankemaPyPI

Advisory published May 8, 2026Updated May 8, 2026

yeahmankema is a confirmed malicious PyPI package (MAL-2026-3386) 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 yeahmankema (PyPI)

MAL-2026-3386

Immediate action

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

pip uninstall yeahmankema

What this malware does

Package exfiltrates screenshots and network information to a hardcoded target.

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

Campaign: 2026-05-crayrandomiz

Reasons (based on the campaign):

exfiltration-generic
obfuscation
spyware-like

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

e82095096c026f9ea1f8a44e7b94b0f9def1346ef887a8a6bb4e11aedc5abd63

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for yeahmankema (2 malicious versions).
If you installed it — respond
yeahmankema 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 yeahmankema 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. yeahmankema 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

2026-05-crayrandomiz

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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