statist-browser-typed-client-itsa.digitalinterview.eventsnpm
statist-browser-typed-client-itsa.digitalinterview.events is a confirmed malicious npm package (MAL-2026-12446) that executes malicious code on install (malicious version 20.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-itsa.digitalinterview.events (npm)
What this malware does
On require, index.js loads init.js which selects an OS/arch-specific staging path, downloads a binary payload from hardcoded Cloudflare Workers hosts assembled by joining split character arrays (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT fallback channel across *.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), writes the bytes to disguised paths such as /var/tmp/.cache<rand> or a Windows Temp/dotnet_diag_<rand>.exe, chmods to 0755, and spawn-detaches /bin/sh (or cmd) to execute the binary in the background. Destination hostnames are obfuscated by array-split-and-join to defeat static scanners; the payload is staged under decoy filenames posing as.NET diagnostics or cache files. A second full copy of the dropper is bundled in lib/telemetry.js (not reached from the current entry graph) using the same base64-decode, chmod 0755, and /bin/sh spawn shape, providing an alternate loader.
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 statist-browser-typed-client-itsa.digitalinterview.events (version 20.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging statist-browser-typed-client-itsa.digitalinterview.events across your stack and pipelines.
If you installed it — respond
Remove statist-browser-typed-client-itsa.digitalinterview.events 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 statist-browser-typed-client-itsa.digitalinterview.events 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 statist-browser-typed-client-itsa.digitalinterview.events 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 statist-browser-typed-client-itsa.digitalinterview.events-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.