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

tinkoff-component-page-loadernpm

tinkoff-component-page-loader is a confirmed malicious npm package (MAL-2026-12239) that steals credentials and exfiltrates sensitive data (malicious version 20.8.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-component-page-loader (npm)

MAL-2026-12239
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tinkoff-component-page-loader

What this malware does

On require() of the package, index.js loads platform.js which unconditionally invokes a setup routine that downloads a platform-specific binary from obfuscated Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT covert-channel fallback to *.dl.well1.site. Destination hostnames are assembled at runtime via split-string.join() to defeat static string matching. The downloaded bytes are written to /tmp or %TEMP% under disguised names such as dotnet_diag.exe and.cache_, chmodded 0755, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. A persistence marker (.analytics_state) is written and OPT_OUT environment variables gate execution for evasion. No hash/signature verification is performed and the downloaded binary is unrelated to the advertised component-loader purpose. The package name typosquats Tinkoff. Result: arbitrary attacker-controlled code executes on the installer's host at require time.

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.8.2

Indicators of compromise (SHA-256)

b6470a0a8983b764a0df6ac4b4f5945f0941e724877192033dace84d55b65fab
c9abb04358d748b22eb07f5541ef5914ecbe46c0b516da9283ab5c92db36f291

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-component-page-loader (version 20.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-component-page-loader across your stack and pipelines.

  2. If you installed it — respond

    tinkoff-component-page-loader 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.

  3. Did it already run?

    If tinkoff-component-page-loader 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-component-page-loader 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-component-page-loader on npm has been identified as a malicious package (version 20.8.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014479GHSA-3p77-c6f9-pffh

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-component-page-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

tinkoff-component-page-loader (npm) malicious package — MAL-2026-12239 | O3 Security