# MAL-2026-11400: Malicious code in thedata (npm)


- **Type:** Malicious package
- **Package:** `thedata` (npm)
- **Published:** 30 Jul 2026
- **Also known as:** GHSA-g67p-r2r2-224w

## What is MAL-2026-11400?

MAL-2026-11400 is a malicious package in thedata, published on 30 Jul 2026. 

### Official description

The package's main entry (index.js) re-exports two values, rsaKey and desKey, from apps/docs/app/theta.js, which simply readFileSync's apps/docs/app/rsa.db and apps/docs/app/des.db as UTF-8 strings. Both.db files are base64-encoded OpenSSL 'Salted__' ciphertext. The package contains no code that decrypts, uses, or otherwise interacts with these blobs, and no documented API beyond exposing them. The package name resembles 'Theta Data' per the README but the shipped functionality does not implement any such client. Installing or importing thedata by itself performs no network activity, no filesystem access outside its own directory, no credential reads, and no code execution — the encrypted payloads are inert unless a separate consumer supplies the decryption key. The shape (a nearly-empty library whose only purpose is to serve opaque encrypted content to another party) is unusual for a legitimate library but does not by itself establish installer harm from this package alone.

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

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

## Sources

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

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