Which versions of pystallerer are malicious?

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

How do I remediate pystallerer if I installed it?

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

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

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

Malicious package

pystallererPyPI

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

MAL-2023-8585

Immediate action

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

pip uninstall pystallerer

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b5a51d76ce9c25a9173b53083249e289f894f767751f075d7d9bf112d946a7ee

e4c5066aedf882caac200565f905a0f23a4776cf6c3d4dd2412ba0ee902840d5

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

Campaign

RLMA-2024-04575

References

Credits

Checkmarx · finder
ReversingLabs · finder

Detect & block this

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