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

documenclientnpm

Advisory published Updated

documenclient is a confirmed malicious npm package (MAL-2026-17624) that executes malicious code on install (malicious versions 1.0.4, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in documenclient (npm)

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

What this malware does

[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.

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

2 flagged
1.0.41.0.5

Indicators of compromise (SHA-256)

fd77316cd00f6397a05779a443f939cd3a5e09efa8321c7d52bd4623ffe2855f
ffd20318a8d48dc20fee95097373ebd1039481031985164a651d2b68d366565a
19f38811cd4bf975caf3f28d03d68dd1ff023af34ef94d700edf22fb731d59dc

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for documenclient (2 malicious versions).

  2. If you installed it — respond

    Remove documenclient 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 documenclient 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. documenclient on npm has been identified as a malicious package (versions 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-648r-w4vm-vvvpIN-MAL-2026-021126IN-MAL-2026-021128

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks documenclient-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

documenclient (npm) malicious package — MAL-2026-17624 | O3 Security