Which versions of discordnv are malicious?

The following PyPI versions of discordnv are flagged malicious: 0.8.0. Treat any of these as compromised.

How do I remediate discordnv if I installed it?

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

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

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

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

Malicious package

discordnvPyPI

discordnv is a confirmed malicious PyPI package (MAL-2026-11050) that steals credentials and exfiltrates sensitive data (malicious version 0.8.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in discordnv (PyPI)

MAL-2026-11050

Immediate action

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

pip uninstall discordnv

What this malware does

On import discordnv, init.py invokes main_entry() which hides the console window, walks Discord/Chrome/Edge/Brave/Opera/Yandex/Firefox LevelDB/SQLite stores to extract Discord authentication tokens, reads and DPAPI-decrypts Roblox robloxcookies.dat, and POSTs the harvested credentials to a hardcoded Discord webhook at discord.com/api/webhooks/1528403989983662194/... and a Google Apps Script endpoint at script.google.com/macros/s/AKfycbwa.../exec. add_to_startup() writes an HKCU\Software\Microsoft\Windows\CurrentVersion\Run entry named discordnv pointing at the invoking Python/exe so the stealer re-runs on every user logon. All operations are wrapped in bare try/except to swallow errors and avoid alerting the user. The package's advertised purpose (a Roblox DataStore helper) is unrelated to the observed behavior.

The package exfiltrates Roblox cookies and Discord tokens 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.8.0

Indicators of compromise (SHA-256)

d28ded2ca28c0182385e9dccf5939e883fd5f18dfa702ca912429270a92f3646

2f79139609558d677545faa7d5f1d30ec31a54abe9fba990117ec0d27ea3ba48

37f22bdde7806be47d48be729a446864a79e9357f1ea5ef2140b8004929597f0

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

Campaign

2026-06-spaysrbdataIN-MAL-2026-011050

References

Credits

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

Detect & block this

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