# MAL-2026-10868: Malicious code in neroteam-v1 (PyPI)


- **Type:** Malicious package
- **Package:** `neroteam-v1` (PyPI)
- **Published:** 20 Jul 2026

## What is MAL-2026-10868?

MAL-2026-10868 is a malicious package in neroteam-v1, published on 20 Jul 2026. 

### Official description

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.

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

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-10868 is a malicious package: neroteam-v1 (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-10868/ (Markdown: https://insights.sbomify.com/MAL-2026-10868/index.md)
```

## Sources

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

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