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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spaysrbdata (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spaysrbdata across your stack and pipelines.

Malicious package

spaysrbdataPyPI

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

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

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 spaysrbdata (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spaysrbdata across your stack and pipelines.
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 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 spaysrbdata 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. 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