Which versions of spaysdata are malicious?

The following PyPI versions of spaysdata are flagged malicious: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.4.2, 0.4.4, 0.4.5. Treat any of these as compromised.

How do I remediate spaysdata if I installed it?

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

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

Yes — spaysdata is associated with the 2026-06-spaysrbdata 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 spaysdata across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spaysdata (7 malicious versions).

Part of a larger attack: 2026-06-spaysrbdata published 9 malicious packages. See the full campaign →

Malicious package

spaysdataPyPI

Advisory published Jun 2, 2026Updated Aug 27, 2026

spaysdata is a confirmed malicious PyPI package (MAL-2026-5171) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0, 0.3.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spaysdata (PyPI)

MAL-2026-5171

Immediate action

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

pip uninstall spaysdata

What this malware does

The package exfiltrates Roblox cookies from the victim machine.

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

Campaign: 2026-06-spaysrbdata

Reasons (based on the campaign):

infostealer

Malicious versions

7 flagged

0.1.00.2.00.3.00.4.00.4.20.4.40.4.5

Indicators of compromise (SHA-256)

55bfbc1a93fe9a662ed20b5fb651390a850c8f43e4d68d81677b4ffd0ca17bcf

7c4f20bacc240589b8c9660a0b722f173309c6cd42cf577c7de2e4ee1e4009a1

68ef1b204fe6ceac8987ad92597c4f1a6b9549256bcf2db652ab97574eaab998

db1b035fe5bfbcc9edb3bbf9e0c89018c3bf03e9725997eee60db7f8cd7b3d70

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for spaysdata (7 malicious versions).
If you installed it — respond
spaysdata 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 spaysdata 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. spaysdata on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.4.2, 0.4.4, 0.4.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-spaysrbdata

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database