neroteam-v1PyPI
neroteam-v1 is a confirmed malicious PyPI package (MAL-2026-10868) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in neroteam-v1 (PyPI)
What this malware does
Importing the nero package triggers nero/__init__.py to load nero.main, whose top-level code runs a _guard() routine before executing a hidden payload. _guard() performs anti-debug checks (sys.gettrace, sys.settrace(None), _getframe().f_trace), timing checks, and substring matching against sandbox/VM indicators (sandbox, virtualbox, vmware, qemu, wine, hyperv, xen) in PATH, the Python executable path, and processor identifiers. It then base64-decodes a ~110KB blob, decrypts it with a custom RC4-like keystream cipher keyed by the string Cxdgs, and passes the plaintext to exec(). The decrypted code is opaque and only reachable on machines that pass the anti-analysis gauntlet. The combination of import-time exec of a custom-encrypted blob with dedicated anti-VM and anti-debug evasion is inconsistent with the package's stated 'account generator' purpose and matches the shape of hostile install/import-time code execution against the installer's host.
Obfuscated code is used to abuse systems of garena[.]com for mass account generation, bypassing their security systems.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-07-neroteam-v1
Reasons (based on the campaign):
-
obfuscation
-
abusing-3rd-api
-
The package contains code to detect if it is running in a sandbox environment.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for neroteam-v1 (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging neroteam-v1 across your stack and pipelines.
If you installed it — respond
neroteam-v1 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 neroteam-v1 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 neroteam-v1 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks neroteam-v1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.