Malicious code in expect-dotenv (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14316
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ffc39d28e4d33afe723182c097769f087bf528732e5468b1511bf2bff41db01e) The package's main entry runs a worker that performs an HTTPS GET to https://realase-0626.vercel.app/api/v1 and passes the response's `parser` string into vm.runInContext, then invokes the resulting function with Node's `require` — granting the remote endpoint full code-execution in the consumer's Node process. The destination URL is concealed as a hex byte array in constants.js (pluginIDs) and reassembled at runtime via String.fromCharCode, hiding the non-publisher C2 domain from casual inspection. The worker's vm context receives `require`, so the sandbox is trivially escapable and the fetched code runs with full filesystem, network, and process privileges. This behavior fires on `require('expect-dotenv')` followed by `.config()` or `.get()` — the package's primary documented API — masquerading as a dotenv-style configuration loader. ## Source: ghsa-malware (3902298c6bf94b97a0e9eb6de4e59555e036d923501e138f6420ea0320290aee) 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.
- Source published
- 20 Aug 2026 03:32:44 UTC
- Source modified
- 14 Sep 2026 20:30:05 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.