Which versions of spaysrbx are malicious?

The following PyPI versions of spaysrbx are flagged malicious: 0.3.0. Treat any of these as compromised.

How do I remediate spaysrbx if I installed it?

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

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

Yes — spaysrbx is associated with the 2026-06-spaysrbdata, IN-MAL-2026-005373 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 spaysrbx 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 spaysrbx (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spaysrbx across your stack and pipelines.

Malicious package

spaysrbxPyPI

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

MAL-2026-5334

Immediate action

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

pip uninstall spaysrbx

What this malware does

On import spaysdata, the package's __init__.py invokes main_entry() in spaysdata/main.py, which performs three attacker-benefit actions automatically: (1) reads %USERPROFILE%/AppData/Local/Roblox/LocalStorage/robloxcookies.dat, decrypts it via win32crypt.CryptUnprotectData, and POSTs the cleartext Roblox session cookies to a hardcoded Discord webhook (discord.com/api/webhooks/1513603677913616544/...); (2) enumerates Discord, Discord Canary, Lightcord, Chrome, Edge, Brave, Yandex, Opera, and Firefox profile directories, decrypts dQw4w9WgXcQ-encrypted tokens using DPAPI + AES-GCM, kills Discord.exe via taskkill, and POSTs each token plus user info to the same webhook; (3) copies the running file to %APPDATA%/MySystemUtility/ and writes HKCU\Software\Microsoft\Windows\CurrentVersion\Run\MyPythonAutostartApp to re-execute the stealer on each user login, with the console window hidden via ShowWindow(0). The package's advertised purpose (pyproject.toml description: "Library for working with DataStore in Roblox") is a cover story — no DataStore functionality exists in the source; only credential-theft and persistence code is shipped.

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

1 flagged

0.3.0

Indicators of compromise (SHA-256)

21c6a7c2bf656df8e570edbe60daa7af52e1e0df0eae906de41f47dcf6eb0ede

e8ed2b72d0419496418ee74f0479cca2dc8027c6a290c7022d590fb6a57d5780

d4bae51ef6cd61eb9bfc38ac2d8dd8ad1f38d22c4e55b8ccdfc53cd2ed94076f

2a77351a6614c3538a62607e315f0f51a8db3f390f7ee6650b2442b8ee88bc4c

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

Campaign

2026-06-spaysrbdataIN-MAL-2026-005373

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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