Which versions of spaysrbdata are malicious?

The following PyPI versions of spaysrbdata are flagged malicious: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0. Treat any of these as compromised.

How do I remediate spaysrbdata if I installed it?

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

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

Yes — spaysrbdata 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 spaysrbdata across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spaysrbdata (5 malicious versions).

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

Malicious package

spaysrbdataPyPI

Advisory published Jun 2, 2026Updated Aug 27, 2026

spaysrbdata is a confirmed malicious PyPI package (MAL-2026-5170) 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 spaysrbdata (PyPI)

MAL-2026-5170

Immediate action

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

pip uninstall spaysrbdata

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

5 flagged

0.1.00.2.00.3.00.4.00.5.0

Indicators of compromise (SHA-256)

2d461e4f26b3a0fb04120613c34e74745f6d63ce83abe98c40e470c527921501

d0f4585e881e5184a3c3df035360ed6aa879d920f696e089580568249d99646b

5f780e7753cb79b0dc45e5c2213703ea625f9162524a48de0ca9cfbfacbee475

efe13c6382b2f3c0ed29fbc1eb6d69eb0ce130539215fd0332b3f06210c971a3

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for spaysrbdata (5 malicious versions).
If you installed it — respond
spaysrbdata 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 spaysrbdata 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. spaysrbdata on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0 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 spaysrbdata-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