Which versions of core-dotenv are malicious?

The following npm versions of core-dotenv are flagged malicious: 1.4.1. Treat any of these as compromised.

How do I remediate core-dotenv if I installed it?

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.

I already installed core-dotenv — how do I know if it already compromised me?

If core-dotenv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is core-dotenv part of a known attack campaign?

Yes — core-dotenv is associated with the IN-MAL-2026-010614, GHSA-h5mc-5vgx-x5xq campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find core-dotenv across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for core-dotenv (version 1.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging core-dotenv across your stack and pipelines.

Malicious package

core-dotenvnpm

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for core-dotenv (version 1.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging core-dotenv across your stack and pipelines.
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.
Did it already run?
If core-dotenv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks core-dotenv before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database