Which versions of popeye-shyam-love are malicious?

The following PyPI versions of popeye-shyam-love are flagged malicious: 1.0.15. Treat any of these as compromised.

How do I remediate popeye-shyam-love if I installed it?

Remove popeye-shyam-love from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed popeye-shyam-love — how do I know if it already compromised me?

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

Yes — popeye-shyam-love is associated with the GENERIC-simple-tests 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 popeye-shyam-love 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 popeye-shyam-love (version 1.0.15). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging popeye-shyam-love across your stack and pipelines.

Malicious package

popeye-shyam-lovePyPI

Malicious code in popeye-shyam-love (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12327

Immediate action

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

pip uninstall popeye-shyam-love

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.15

Indicators of compromise (SHA-256)

d410a8cc5e057d5a0d02f2b434761fb288793a94557cd49a20430f39f114e2e0

3eb788819517c48b546562559edfe038373cacc957f84f6b3647f9bfaedf0335

f1feb40d0c5e1c6ecdba2edd73f9a58731c92164a1e918ba968a88ed1a9a49e4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for popeye-shyam-love (version 1.0.15). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging popeye-shyam-love across your stack and pipelines.
If you installed it — respond
Remove popeye-shyam-love from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If popeye-shyam-love 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 popeye-shyam-love 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. popeye-shyam-love on PyPI has been identified as a malicious package (version 1.0.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks popeye-shyam-love-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring