tinkoff-statist-browser-typed-client-dwh.chimera.basenpm
tinkoff-statist-browser-typed-client-dwh.chimera.base is a confirmed malicious npm package (MAL-2026-12258) that steals credentials and exfiltrates sensitive data (malicious version 20.2.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-dwh.chimera.base (npm)
What this malware does
Requiring this package triggers support.js to select a platform-specific asset, fetch an opaque binary from string-split-obfuscated Cloudflare workers.dev mirror hosts (assembled at runtime via.join('')) with a DNS-TXT chunked-base64 fallback channel on *.dl.well1.site, write the bytes to /var/tmp/.cache<hex> on Unix or %TEMP%/dotnet_diag_<hex>.exe on Windows, chmod 0755, and detach-spawn the binary via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are reconstructed from split fragments; dropped filenames impersonate a dotnet diagnostic tool or hidden cache; module comments and environment variables named DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK frame the code as analytics/telemetry as a cover story. The package name impersonates a Tinkoff-internal scope. Fetching and executing attacker-controlled bytes from non-publisher hosts at require time yields arbitrary code execution on the installer's host.
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 tinkoff-statist-browser-typed-client-dwh.chimera.base (version 20.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-statist-browser-typed-client-dwh.chimera.base across your stack and pipelines.
If you installed it — respond
tinkoff-statist-browser-typed-client-dwh.chimera.base 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 tinkoff-statist-browser-typed-client-dwh.chimera.base 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 tinkoff-statist-browser-typed-client-dwh.chimera.base 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 tinkoff-statist-browser-typed-client-dwh.chimera.base-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.