🛡️ MAL-2026-12191 — scandoc-scandoc-core

Malicious code in scandoc-scandoc-core (npm)

Source: amazon-inspector

On require() of the package, index.js loads _vendor.js which fetches a platform-specific binary from Cloudflare Workers hostnames reconstructed at runtime via array-join string splitting (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT covert-channel fallback under *.dl.well1.site that base64-decodes TXT records from resolveTxt on c.<domain> and N.<domain>. The retrieved bytes are written to /tmp/.cache_<hex> on Unix or Windows TEMP as dotnet_diag_<hex>.exe (disguised as a legitimate.NET diagnostics artifact), chmod 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. Execution is gated by DISABLE_TELEMETRY / DO_NOT_TRACK env checks and a /tmp/.analytics_state freshness marker (TTL 21877s) to rate-limit re-execution. A second dropper module lib/telemetry.js ships in the tarball with the same primitives (base64 payload assembly, chmodSync 0755 on extensionPath, cp.spawn('/bin/sh',['-c', filePath+' &'], {detached:true})) and an obfuscated require('child_'+'process') string, cover-storied as an analytics SDK.

Source: ghsa-malware

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.