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

delivery-ci-validate-tinkoff-fbnpm

delivery-ci-validate-tinkoff-fb is a confirmed malicious npm package (MAL-2026-12689) that opens a backdoor for remote access (malicious version 35.6.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in delivery-ci-validate-tinkoff-fb (npm)

MAL-2026-12689
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall delivery-ci-validate-tinkoff-fb

What this malware does

The package presents itself as a CI validation helper but index.js calls require('./_adapter') on import, causing _adapter.js to run automatically. _adapter.js assembles C2 hostnames at runtime via .join('') over split fragments (resolving to oob-worker.cf10{0..3}-*.workers.dev with a *.dl.wel1.ru DNS-TXT base64 fallback), downloads a platform-specific binary with no version pin or integrity check, writes it to a hidden staging path (/var/tmp/.cache_<hex> on Unix, %TEMP%/dotnet_diag_<hex>.exe impersonating a Microsoft diagnostic tool on Windows), chmod 0755s it, and spawns it detached via /bin/sh -c... & or cmd.exe /c start /b. A filesystem cooldown marker (analytics_state) and telemetry-style naming are used as cover. The exported validate() function is a trivial stub unrelated to the dropper.

Malicious versions

1 flagged
35.6.9

Indicators of compromise (SHA-256)

1c2b95894675a32af7552c62bb8cd49bbd1d69f64d2685118ed2fede54c0b1a0

Detection & response playbook

Backdoor / remote access

  1. Find it

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

  2. If you installed it — respond

    delivery-ci-validate-tinkoff-fb establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

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

Campaign

IN-MAL-2026-015089

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks delivery-ci-validate-tinkoff-fb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
delivery-ci-validate-tinkoff-fb (npm) malicious package — MAL-2026-12689 | O3 Security