Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

core-dotenvnpm

Advisory published Updated

core-dotenv is a confirmed malicious npm package (MAL-2026-10631) that executes malicious code on install (malicious version 1.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in core-dotenv (npm)

MAL-2026-10631
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall core-dotenv

What this malware does

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.

Malicious versions

1 flagged
1.4.1

Indicators of compromise (SHA-256)

aad83962ee4db02c1bf43558ed5fe6bf79f66754b070415223d29643a8ff754e
eaaf60fe0a946f83e4b6ff554a0061181dc799809975f214e6eb8d44fa7f6c9d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for core-dotenv (version 1.4.1).

  2. If you installed it — respond

    Remove core-dotenv from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If core-dotenv was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. core-dotenv on npm has been identified as a malicious package (version 1.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010614GHSA-h5mc-5vgx-x5xq

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks core-dotenv-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

core-dotenv (npm) malicious package — MAL-2026-10631 | O3 Security