Which versions of popeye-pip-v3 are malicious?

The following PyPI versions of popeye-pip-v3 are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate popeye-pip-v3 if I installed it?

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

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

Yes — popeye-pip-v3 is associated with the RLMA-2024-08770, 2024-01-moye-moye, RLUA-2026-00599 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-pip-v3 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-pip-v3 (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging popeye-pip-v3 across your stack and pipelines.

Malicious package

popeye-pip-v3PyPI

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

MAL-2024-10105

Immediate action

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

pip uninstall popeye-pip-v3

What this malware does

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-01-moye-moye

Reasons (based on the campaign):

exfiltration-ssh-keys
exfiltration-env-variables
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

a7a9ce4cd94cb5a57ba8a09af77389f3c011f732cee52ebeb951c518de738aca

0a4769d7788bb3797b628ce45eaef49bd3beb2bc3e884fbd93c7897a3f5d66fe

940ada25d3157d4f88092627a5a8eedb98abf86933890ce13193d4878d2698ee

9a333a0e0b4d06c09c019715bed11d7861602dea23cf0d0311795076cfb4aae6

e80b79d472a29b102c5ee1fd26181f352253575d7ebc1badc7df9067ffa4a845

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

Campaign

RLMA-2024-087702024-01-moye-moyeRLUA-2026-00599

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks popeye-pip-v3-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