hubert-application-get-document-preview-amnpm
hubert-application-get-document-preview-am is a confirmed malicious npm package (MAL-2026-11540) that executes malicious code on install (malicious version 20.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hubert-application-get-document-preview-am (npm)
What this malware does
On require() of the package, index.js loads setup.js which selects a platform key, downloads a native binary from one of four hardcoded workers.dev endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel over *.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), writes the payload to /tmp or %TEMP% under deceptive names such as dotnet_diag_<rand>.exe and.cache_<rand>, chmods it 755, and spawns it detached via /bin/sh -c or cmd. The hostnames are reconstructed at runtime by array.join('') to evade static analysis; the DNS-TXT channel reassembles base64 chunks from N.<domain> TXT records as a covert transport when HTTPS is blocked. No hash or signature verification is performed, and the destinations are unrelated to any legitimate package publisher. A second self-contained dropper bundled in lib/telemetry.js (framed as an 'Analytics SDK') contains duplicate machinery — require("child_"+"process"), base64 chunk decoding, fs['chmod'+'Sync'] to 0755, and cp.spawn('/bin/sh',['-c', filePath+' &']) — providing an alternate execution path.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hubert-application-get-document-preview-am (version 20.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hubert-application-get-document-preview-am across your stack and pipelines.
If you installed it — respond
Remove hubert-application-get-document-preview-am 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 hubert-application-get-document-preview-am 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 hubert-application-get-document-preview-am 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks hubert-application-get-document-preview-am-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.