dwhetlfront-dwhetlfront-corenpm
dwhetlfront-dwhetlfront-core is a confirmed malicious npm package (MAL-2026-13202) that steals credentials and exfiltrates sensitive data (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dwhetlfront-dwhetlfront-core (npm)
What this malware does
On require() of the package, index.js loads support.js which selects a platform-specific payload URL, downloads bytes from Cloudflare workers.dev hosts (oob-worker.cf10{0-3}-*.workers.dev) with a DNS-TXT chunked-base64 fallback under {sdk,ext,pkg,net}.dl.wel1.ru, writes the bytes to /tmp or %TEMP% under a cover-story filename (dotnet_diag.exe,.cache_), chmods 0755, and spawns the file detached via cp.spawn('/bin/sh', ['-c', path + ' &'], {detached:true}) or spawn('cmd',...). Destination hostnames are reconstructed at runtime via array-join splits (e.g., ['sdk','.d','l.wel1','.r','u'].join('') and ['oob-w','orker.cf100-416.worker','s.','dev'].join('')) and API names such as 'child_' + 'process' are string-concatenated to evade static analysis. A lock file gates repeat execution and an opt-out env var serves as a cover story. A parallel dropper implementation exists in lib/telemetry.js (base64 chunk assembly, sh -c spawn, chmod 755 via bracketed 'chmod'+'Sync'); it is not reached from index.js in this version but is bundled in the tarball.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dwhetlfront-dwhetlfront-core (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dwhetlfront-dwhetlfront-core across your stack and pipelines.
If you installed it — respond
dwhetlfront-dwhetlfront-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dwhetlfront-dwhetlfront-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 dwhetlfront-dwhetlfront-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 dwhetlfront-dwhetlfront-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.