# MAL-2026-15878: Malicious code in cbc97b7a (npm)


- **Type:** Malicious package
- **Package:** `cbc97b7a` (npm)
- **Published:** 3 Sep 2026
- **Also known as:** GHSA-9m3c-67f2-gjwf

## What is MAL-2026-15878?

MAL-2026-15878 is a malicious package in cbc97b7a, published on 3 Sep 2026. 

### Official description

The tarball ships only package.json with no code, scripts, main, or bin. The description field contains a ~41KB base64-encoded POSIX shell script that, when decoded and executed, downloads an xmrig cryptominer from gitlab.com/albertotrindade131/al and a github.com/lucas77335/xmrig-amd mirror, installs cron-based persistence, and mines Monero to the hardcoded pool xmr.kryptex.network:8029 with an embedded wallet/worker identifier. Operational strings (pool host, wallet, miner URLs, fallback bare-IP C2 hosts 66.23.199.44, 45.94.31.89, 139.59.59.33, 154.89.152.115, 84.21.173.223, 142.132.131.238) are individually base64-encoded and decoded at runtime via a helper function. The payload script self-references https://registry.npmjs.org/cbc97b7a/latest, indicating the package is designed to be pulled by a companion loader that fetches this metadata and pipes the decoded description to sh, delivering miner installation, persistence, and secondary C2 fetches to the installer.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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

## Sources

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

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