Which versions of pyefflorer are malicious?

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

How do I remediate pyefflorer if I installed it?

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

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

Yes — pyefflorer is associated with the RLMA-2024-04488 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 pyefflorer 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 pyefflorer (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyefflorer across your stack and pipelines.

Malicious package

pyefflorerPyPI

Malicious code in pyefflorer (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2023-8570

Immediate action

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

pip uninstall pyefflorer

What this malware does

Malicious packages campaign targeting developers, payload is hidden using Steganography, exfiltrate host information

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

9db59fb1fff1df375feb9a17164f004b62a2d5fa194dcc285341536b6bfb51aa

eca396a5a824b7e16bb60ccf05f1619c55d8e6c3457ac12b443bede4bc81a6e1

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

Campaign

RLMA-2024-04488

References

Credits

Checkmarx · finder
ReversingLabs · finder

Detect & block this

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