scandoc-scandoc-corenpm
scandoc-scandoc-core is a confirmed malicious npm package (MAL-2026-12191) that executes malicious code on install (malicious version 20.8.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in scandoc-scandoc-core (npm)
What this malware does
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.
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
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 scandoc-scandoc-core (version 20.8.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scandoc-scandoc-core across your stack and pipelines.
If you installed it — respond
Remove scandoc-scandoc-core 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 scandoc-scandoc-core 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 scandoc-scandoc-core 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 scandoc-scandoc-core-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.