Which versions of spokeo are malicious?

The following PyPI versions of spokeo are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate spokeo if I installed it?

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

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

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

Malicious package

spokeoPyPI

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

MAL-2025-6594

Immediate action

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

pip uninstall spokeo

What this malware does

Installing source package or importing the module starts downloading and running an external executable, which is widely recognized as malware

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

Campaign: 2025-06-spokeo

Reasons (based on the campaign):

impersonation
malware
Downloads and executes a remote executable.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

458c0a90e98d4eb72f009103d6d274f95d6c9b45d0c901bbedcfd0285383d2ec

6401bcba5e78dcabb67d5bead6d91744023e47220bdaf7d6b97a883191dc2f61

77e85dedb987a603a027306a57e7b988de52be0c9f12fc2a04dfacf5e3adcd19

622ddd5faac7083f5e3f2b996c9038b23450c24ead5e2a6fddd3006bc78306d3

01781a41fe172d566c38d4e360076155aa24f33ea5bd85af1f02569c61b7fb2a

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

Campaign

RLMA-2025-036932025-06-spokeoRLUA-2026-00777

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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