Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocksnpm

tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks is a confirmed malicious npm package (MAL-2026-12259) that typosquats a legitimate package to trick installs (malicious version 20.4.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks (npm)

MAL-2026-12259
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks

What this malware does

On require() of this package, index.js loads _vendor.js which downloads a platform-specific binary from runtime-assembled Cloudflare Workers hostnames (built by split-and-join of string fragments, with DNS-TXT fallback via *.dl.well1.site subdomains), writes it to a hidden path under /tmp or %TEMP% using disguised filenames (.cache_<uid> on POSIX, dotnet_diag_<uid>.exe on Windows), sets mode 755 via fs.chmodSync, and spawns it detached with cp.spawn('/bin/sh', ['-c', path+' &'], {detached:true}).unref() or cmd.exe start /b. A second variant of the same drop-and-execute chain is shipped in lib/telemetry.js (base64 chunk assembly, chmod 755, /bin/sh spawn) behind an 'analytics SDK' framing, callable if that module is imported directly. Hostname assembly and filename impersonation of benign diagnostic artifacts (dotnet_diag_*, .analytics_state stamp file) are evasion patterns rather than telemetry behavior. Installing or requiring this package results in execution of attacker-controlled, unverified binary code on the installer host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
20.4.7

Indicators of compromise (SHA-256)

2d381f80d9b2d3b310ab426d3c51996861b4c320f2926e53ea078da80e832a07
acfca628e45d043943b03d525b8c51e3fcb5cac96f4ce979180b9953bf1ef717

Detection & response playbook

Typosquat
  1. Find 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-eventea.projects.finhealthwebmicroblocks (version 20.4.7). 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-eventea.projects.finhealthwebmicroblocks across your stack and pipelines.

  2. If you installed it — respond

    tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks 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.

  4. How O3 protects you

    O3 blocks tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks 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

No. tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks on npm has been identified as a malicious package (version 20.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014526GHSA-7q2v-5fj7-w9mg

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks-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.

Explore

tinkoff-statist-browser-typed-client-eventea.projects.finhealthwebmicroblocks (npm) malicious package — MAL-2026-12259 | O3 Security