Which versions of superline are malicious?

The following PyPI versions of superline are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate superline if I installed it?

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

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

Yes — superline is associated with the RLMA-2025-01239, 2025-01-superline, RLUA-2026-00788 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 superline 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 superline (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging superline across your stack and pipelines.

Malicious package

superlinePyPI

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

MAL-2025-1996

Immediate action

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

pip uninstall superline

What this malware does

Importing the package starts an advanced Infostealer, probably Blank Grabber, exfiltrating browser data, wifi passwords, discord and games tokens, crypto wallets etc.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-01-superline

Reasons (based on the campaign):

exfiltration-browser-data
infostealer
exfiltration-generic
peristence-autorun
exfiltration-crypto
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

b210e097c26dad5e2008df741bf344636b53a7737e09d586f56334b3f6e684a8

6b3ff5f0b7a3cca0b925828c2073d18c26a229abf5a51ce88f892557ef8f476d

59df95892042deb7d9fd8ce71d1890aeafd0cdab2cb8bbc3948504e74ccae39e

2a25715177382da7b2fc216c8e9f116e40c3bd383591ae5dcb36c51df7d1c8a0

af89b494a9c9d66ddcf2157d5b0c67cf8f2a122bc4d30e6d53ccaf1559c8da78

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

Campaign

RLMA-2025-012392025-01-superlineRLUA-2026-00788

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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