# MAL-2026-5334: Malicious code in spaysrbx (PyPI)


- **Type:** Malicious package
- **Package:** `spaysrbx` (PyPI)
- **Published:** 8 Jun 2026

## What is MAL-2026-5334?

MAL-2026-5334 is a malicious package in spaysrbx, published on 8 Jun 2026. 

### Official description

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

## What should I do about MAL-2026-5334?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5334 is a malicious package: spaysrbx (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5334/ (Markdown: https://insights.sbomify.com/MAL-2026-5334/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5334

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5334/
Summaries are generated and may contain mistakes; the official description above is the record.