statist-browser-typed-client-jumptaxi.feature.contactsnpm
statist-browser-typed-client-jumptaxi.feature.contacts is a confirmed malicious npm package (MAL-2026-12309) that executes malicious code on install (malicious version 20.7.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-jumptaxi.feature.contacts (npm)
What this malware does
On require of the package (index.js loads./vendor at import), vendor.js selects a platform-specific staging path, downloads a binary from a rotated list of Cloudflare workers.dev origins whose hostnames are reconstructed at runtime from split-string arrays joined together, with a DNS TXT covert-channel fallback that reassembles base64 chunks from numbered subdomains under dl.well1.site. The fetched bytes are written to /var/tmp or %TEMP% under cover-story filenames (.cache<rand>, dotnet_diag<rand>.exe,.analytics_state), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. No hash or signature verification is performed and destinations are not first-party publisher infrastructure. Any consumer that imports this package auto-executes an attacker-controlled native payload on the installer's host.
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-jumptaxi.feature.contacts (version 20.7.7). 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-jumptaxi.feature.contacts across your stack and pipelines.
If you installed it — respond
Remove statist-browser-typed-client-jumptaxi.feature.contacts 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-jumptaxi.feature.contacts 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-jumptaxi.feature.contacts 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-jumptaxi.feature.contacts-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.