statist-browser-typed-client-nfs.grocery.mobile.eventsnpm
statist-browser-typed-client-nfs.grocery.mobile.events is a confirmed malicious npm package (MAL-2026-12074) that steals credentials and exfiltrates sensitive data (malicious version 20.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-nfs.grocery.mobile.events (npm)
What this malware does
On require() of the package's main entry, index.js transitively loads platform.js, which selects a platform-specific payload URL, fetches opaque executable bytes from one of three anonymous Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), falls back to a base64-chunked DNS TXT covert channel under *.dl.well1.site (tin/tina/ldr/win subdomains), writes the bytes to /var/tmp or %TEMP% under disguised names (.cache<rand>, dotnet_diag_<rand>.exe), sets 0755 permissions, and detach-spawns them via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true}) or the Windows cmd equivalent. Destination hostnames and DNS domains are assembled at runtime from split string fragments (e.g. ["oob-w","orker.cf102-","baf.workers.de","v"].join(""), ["ldr.dl.w","el","l1.si","te"].join("")) to evade static analysis; the module also silences its own stderr via a no-op logger. Marker files (.analytics_state) and telemetry-style opt-out env vars (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) are cover-story labeling — the actual behavior is unconditional dropper execution. A sibling module lib/telemetry.js (81 KB, not on the require graph from index.js) ships duplicate drop-and-exec primitives with concatenation-obfuscated API names (require("child_"+"process"), fs"chmod"+"Sync"), staged for later invocation. The package name mimics an internal-scoped path (statist-browser-typed-client-nfs.grocery.mobile.events) consistent with a typosquat/dependency-confusion lure.
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 statist-browser-typed-client-nfs.grocery.mobile.events (version 20.3.3). 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-nfs.grocery.mobile.events across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-nfs.grocery.mobile.events 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 statist-browser-typed-client-nfs.grocery.mobile.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-nfs.grocery.mobile.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-nfs.grocery.mobile.events-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.