dwsai-dwsai-corenpm
dwsai-dwsai-core is a confirmed malicious npm package (MAL-2026-13204) that executes malicious code on install (malicious version 35.8.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dwsai-dwsai-core (npm)
What this malware does
On require('dwsai-dwsai-core'), index.js loads adapter.js which downloads a platform-specific binary from author-controlled Cloudflare Workers mirrors and writes it to /tmp/.cache<rnd> on Linux/macOS or %TEMP%/dotnet_diag_<rnd>.exe on Windows (masquerading as the Microsoft dotnet diagnostic tool). The file is chmodded 0755 and spawned detached via /bin/sh -c or cmd.exe, with stdio ignored and unref(). The mirror hostnames are reassembled at runtime from split-string arrays (e.g. ['oob-worker.cf100-41','6.worke','rs.de','v'].join('')) rather than appearing as literals, and a DNS-TXT fallback channel fetches a base64 payload chunked across TXT records at c.*.dl.wel1.ru via dns.resolveTxt to bypass HTTPS egress filtering. No hash or signature verification is performed on the downloaded binary. Execution is gated behind DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env checks and a cache-stamp at /tmp/.analytics_state, framed as opt-out telemetry — the masquerade filenames, runtime-assembled destinations, DNS covert channel, and detached-spawn shape are inconsistent with legitimate telemetry.
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 dwsai-dwsai-core (version 35.8.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dwsai-dwsai-core across your stack and pipelines.
If you installed it — respond
Remove dwsai-dwsai-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 dwsai-dwsai-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 dwsai-dwsai-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 dwsai-dwsai-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.