Which versions of tinkoff-fb-rf-add-application are malicious?

The following npm versions of tinkoff-fb-rf-add-application are flagged malicious: 20.3.5. Treat any of these as compromised.

How do I remediate tinkoff-fb-rf-add-application if I installed it?

tinkoff-fb-rf-add-application 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.

I already installed tinkoff-fb-rf-add-application — how do I know if it already compromised me?

If tinkoff-fb-rf-add-application 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.

Is tinkoff-fb-rf-add-application part of a known attack campaign?

Yes — tinkoff-fb-rf-add-application is associated with the IN-MAL-2026-014506 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tinkoff-fb-rf-add-application across my projects, lockfiles, and CI pipelines?

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

Malicious package

tinkoff-fb-rf-add-applicationnpm

tinkoff-fb-rf-add-application is a confirmed malicious npm package (MAL-2026-12242) that opens a backdoor for remote access (malicious version 20.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-fb-rf-add-application (npm)

MAL-2026-12242

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tinkoff-fb-rf-add-application

What this malware does

The package's main entry loads bootstrap.js on require(), which downloads a platform-specific executable from string-fragment-obfuscated Cloudflare-workers mirrors (assembled at runtime via array-join, e.g. oob-worker.cf*.workers.dev) with a DNS-TXT chunked base64 fallback under *.dl.well1.site (tin/tina/ldr/win subdomains). The fetched bytes are written to /tmp or %TEMP% under a disguised filename impersonating system binaries (dotnet_diag<tag>.exe on Windows,.cache_<tag> on Unix), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. A lock file.analytics_state and telemetry-shaped env-var opt-outs provide a cover story. The C2 hostnames are constructed from split string fragments to evade static analysis.

Malicious versions

1 flagged

20.3.5

Indicators of compromise (SHA-256)

788686e9aacdc59ec40f42563a7d9ba5020c75d6c724c8bf59623213b51df780

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-fb-rf-add-application (version 20.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-fb-rf-add-application across your stack and pipelines.
If you installed it — respond
tinkoff-fb-rf-add-application 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.
Did it already run?
If tinkoff-fb-rf-add-application 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-fb-rf-add-application 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-fb-rf-add-application on npm has been identified as a malicious package (version 20.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014506

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-fb-rf-add-application-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