tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.eventsnpm
tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.events is a confirmed malicious npm package (MAL-2026-12264) that executes malicious code on install (malicious version 20.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.events (npm)
What this malware does
Package main entry require()'s./adapter on load, which reconstructs Cloudflare workers.dev hostnames and a well1.site fallback domain via split-string array-join, downloads a platform-specific binary (with a DNS TXT base64 reassembly fallback that enumerates c.<domain> for a count and then 0.<domain>..N.<domain> for chunked payload parts), writes it to /var/tmp/.cache<rand> or %TEMP%/dotnet_diag_<rand>.exe, chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. A second dropper in lib/telemetry.js repeats the pattern under an 'Analytics SDK' cover story, using require('child_'+'process'), fs['chmod'+'Sync'], base64 chunk assembly, and cp.spawn('/bin/sh',['-c', filePath+' &'],{detached:true}). Destinations and API surfaces are constructed at runtime via string-splitting to evade static scanners. No binding.gyp, no publisher-owned host, no version pinning, no hash verification, and the cover-story naming (dotnet_diag, extension, Analytics SDK) does not match any documented package purpose.
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 tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.events (version 20.9.9). 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-itsa.corporatemessenger.clientv1.web.events across your stack and pipelines.
If you installed it — respond
Remove tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.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 tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.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 tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.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 tinkoff-statist-browser-typed-client-itsa.corporatemessenger.clientv1.web.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.