Which versions of solscan are malicious?

The following PyPI versions of solscan are flagged malicious: 0.1, 1.0.1, 1.2.2. Treat any of these as compromised.

How do I remediate solscan if I installed it?

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

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

Yes — solscan is associated with the RLMA-2025-02000, RLUA-2025-02536 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 solscan across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for solscan (3 malicious versions).

Malicious package

solscanPyPI

solscan is a confirmed malicious PyPI package (MAL-2025-3001) that executes malicious code on install (malicious versions 0.1, 1.0.1, 1.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solscan (PyPI)

MAL-2025-3001

Immediate action

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

pip uninstall solscan

Malicious versions

3 flagged

0.11.0.11.2.2

Indicators of compromise (SHA-256)

66140a7f246c53bb3b81091cf5418480481a45a00468a917743d29067d553d65

286842cbfb2edeab29a98411c54afba69820efcd2e5e22845bf11723bed2bb10

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-02000RLUA-2025-02536

Credits

ReversingLabs · finder

Detect & block this

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