Which versions of dexscreener-data are malicious?

The following PyPI versions of dexscreener-data are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate dexscreener-data if I installed it?

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

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

Yes — dexscreener-data is associated with the RLMA-2025-03008, 2025-05-solana-token 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 dexscreener-data 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 dexscreener-data (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dexscreener-data across your stack and pipelines.

Malicious package

dexscreener-dataPyPI

Malicious code in dexscreener-data (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-5111

Immediate action

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

pip uninstall dexscreener-data

What this malware does

Code exfiltrates the current python code and/or IPythonshell history

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

Campaign: 2025-05-solana-token

Reasons (based on the campaign):

crypto-related
impersonation
action-hidden-in-lib-usage
exfiltration-crypto

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

0dead69157fdba5fe5d82a4df9325b599755f113603ad6a507d4814fc208c9e4

4b14633a659ae51be74072fffd3075dffe1a86cbda3da6ab94abc5946171cd74

066a4d507cf7468384b144c7aa850b759abf3d38a02a609b42eed723f149f37a

d5bc90aba6faa8e2ba10bcf59351b47c526813846afb50cb77ee90401f7ea9fc

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

Campaign

RLMA-2025-030082025-05-solana-token

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks dexscreener-data-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