Malicious code in documenclient (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ffd20318a8d48dc20fee95097373ebd1039481031985164a651d2b68d366565a) [email protected] publishes an npm package whose only shipped content is a heavily obfuscated PowerShell script embedded in the README. The script hides its console window via ShowWindow(hWnd, 0), positions the window off-screen at (-32000, -32000) via SetWindowPos, sleeps a randomized interval, concatenates ~140 string fragments into a base64 blob, XOR-decodes it with key 89, and executes the resulting payload via reflective [ScriptBlock]::Create invocation assembled from char-code type and method names. The declared main (index.js) is absent and files is empty, so the artifact has no legitimate JavaScript functionality — the dropper script is the entire payload. Console hiding, off-screen window placement, randomized sleep jitter, dynamic type/method resolution, and XOR+base64 layering have no legitimate purpose in an npm README and are canonical dropper and anti-analysis techniques. The decoded payload is not inspectable from the obfuscated form shipped, so the final behavior on a Windows host executing the script is unknown but attacker-controlled. ## Source: ghsa-malware (fd77316cd00f6397a05779a443f939cd3a5e09efa8321c7d52bd4623ffe2855f) 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

5 Oct 2026 17:31:00 UTC

Source modified

8 Oct 2026 04:00:04 UTC

Observed 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

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.