# MAL-2026-10631: Malicious code in core-dotenv (npm)


- **Type:** Malicious package
- **Package:** `core-dotenv` (npm)
- **Published:** 15 Jul 2026
- **Also known as:** GHSA-h5mc-5vgx-x5xq

## What is MAL-2026-10631?

MAL-2026-10631 is a malicious package in core-dotenv, published on 15 Jul 2026. 

### Official description

core-dotenv presents itself as a dotenv/env-var wrapper. On calling the package's config() (or get(), which lazily invokes config()), a worker (plugin.worker.js) issues an HTTPS request to a destination whose URL is hidden as an array of hex byte values and reconstructed at runtime via String.fromCharCode; the decoded host is realase-0626.vercel.app (path /api/v1). The response is JSON-parsed and its `parser` field is passed to vm.runInContext in a context exposing Function, then invoked with Node's `require` as an argument, granting remotely supplied code full Node capabilities on the host that loaded the library. The destination is unrelated to any documented dotenv functionality, the URL is obfuscated to evade static review, and the fetched content is executed rather than treated as data.

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

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

## Sources

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

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