Which versions of steembase are malicious?

The following PyPI versions of steembase are flagged malicious: 1.5.0. Treat any of these as compromised.

How do I remediate steembase if I installed it?

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

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

Yes — steembase is associated with the RLMA-2025-04267, RLUA-2025-04809, RLUA-2025-05640 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 steembase across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for steembase (version 1.5.0).

Malicious package

steembasePyPI

Advisory published Aug 28, 2025Updated Dec 2, 2025

steembase is a confirmed malicious PyPI package (MAL-2025-41769) that executes malicious code on install (malicious version 1.5.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in steembase (PyPI)

MAL-2025-41769

Immediate action

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

pip uninstall steembase

Malicious versions

1 flagged

1.5.0

Indicators of compromise (SHA-256)

864e2e570a137987e29fd5066a3465500a244933ba3792865d13cba56ae3991a

1328024d7511d39b48b2ec45a66edb36d98f0f7d46c41f92ed66a4b1aaedeb0c

ffdd6208ba76b4e05916252100d03c450f0c10895fe397069eedc29d3be7bf3a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for steembase (version 1.5.0).
If you installed it — respond
Remove steembase 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 steembase 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. steembase on PyPI has been identified as a malicious package (version 1.5.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04267RLUA-2025-04809RLUA-2025-05640

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database