# MAL-2026-11181: Malicious code in chain-manager (npm)


- **Type:** Malicious package
- **Package:** `chain-manager` (npm)
- **Published:** 29 Jul 2026
- **Also known as:** GHSA-257g-ggr2-j398

## What is MAL-2026-11181?

MAL-2026-11181 is a malicious package in chain-manager, published on 29 Jul 2026. 

### Official description

The package is advertised as a docs/landing site for 'Theta Data API', but its main entry (index.js) re-exports a single value `desKey` sourced from apps/docs/app/theta.js, which reads apps/docs/app/des.db via readFileSync. The contents of des.db begin with `U2FsdGVkX1...`, the standard prefix for OpenSSL-encrypted base64 output, indicating an opaque ciphertext payload. The package has no lifecycle scripts, no network I/O, no shell execution, and no reads of installer-side credential paths in its reachable code. Installing or importing this package on its own performs no exfiltration and executes no fetched code. The shape — a nearly empty npm package whose only export is an encrypted blob — is inert in isolation but is consistent with a staged-payload carrier intended to be decrypted and executed by a separate companion loader that holds the corresponding key. The mismatch between the README's stated docs-site purpose and the actual single-export-of-ciphertext content is a transparency concern.

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-11181?

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

## Sources

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

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