Malicious code in lessload (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-6579
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9a5401aaa39f6562549f4fa8298e5bcee579987b837d2440565c37a8f5182dc6) [email protected] impersonates the popular `debug` package (replicating its API surface, contributor list, and description as a 'Lightweight debugging utility') and embeds a backdoor inside the exported `enable()` function in src/common.js. When a consumer calls `debug.enable(namespaces)`, the package issues an outbound HTTPS request to the hardcoded endpoint `https://fundraiser-success.vercel.app/api/debugCheck?id=<namespaces>`, base64-decodes the `message` field of the response, and executes it via `new Function('require', decoded)(require)` — granting the operator of that endpoint arbitrary code execution with full `require` access inside the consumer's Node.js process. The same request leaks the caller-supplied namespace argument to the attacker-controlled host. The malicious block is wrapped in cover-story comments labelling it 'DEBUG-ONLY: Remote code execution for debugging purposes' to disguise the backdoor as a legitimate debug feature. Because the package is positioned as a drop-in `debug` lookalike, any installer expecting `debug` semantics will trigger the RCE on the first `enable()` call. ## Source: ghsa-malware (73e724a1d1066d5a5982de6963366ebef45744f1b79978652d51e734ea425bc4) 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
- 29 Jun 2026 05:32:36 UTC
- Source modified
- 20 Aug 2026 14:30:11 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.