Which versions of bigops-tinkoff-telephony-mock are malicious?

The following npm versions of bigops-tinkoff-telephony-mock are flagged malicious: 35.5.1. Treat any of these as compromised.

How do I remediate bigops-tinkoff-telephony-mock if I installed it?

bigops-tinkoff-telephony-mock is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-tinkoff-telephony-mock, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed bigops-tinkoff-telephony-mock — how do I know if it already compromised me?

If bigops-tinkoff-telephony-mock 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 bigops-tinkoff-telephony-mock part of a known attack campaign?

Yes — bigops-tinkoff-telephony-mock is associated with the IN-MAL-2026-015537, GHSA-92wj-cj5h-gp6p 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 bigops-tinkoff-telephony-mock 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 bigops-tinkoff-telephony-mock (version 35.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-tinkoff-telephony-mock across your stack and pipelines.

Malicious package

bigops-tinkoff-telephony-mocknpm

bigops-tinkoff-telephony-mock is a confirmed malicious npm package (MAL-2026-12847) that typosquats a legitimate package to trick installs (malicious version 35.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-tinkoff-telephony-mock (npm)

MAL-2026-12847

Immediate action

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

npm uninstall bigops-tinkoff-telephony-mock

What this malware does

On require() of the package, index.js loads runtime.js which fetches a platform-specific binary from Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev and siblings) reconstructed at runtime from split string fragments, with a DNS TXT covert-channel fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under names disguised as.NET diagnostics files (dotnet_diag.exe,.cache_), chmod'd 0755, and executed detached via /bin/sh -c '<path> &' or cmd /c start. No hash or signature verification is performed, and the destination hosts are unrelated to the package publisher. A second copy of the same dropper is bundled under lib/telemetry.js wrapped as a fake Sentry-like telemetry SDK. The package name mimics a Tinkoff telephony mock but the shipped code is a full-host remote-code-execution dropper against any machine that installs or imports it.

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

35.5.1

Indicators of compromise (SHA-256)

29cb54c5f503b1cad2b4ae932f592d8870df743b1c1b6b029616343b65f6ae09

38ba2813b46d8ed2bbdfceb6066bfecd7e32d7929f73906e88051b03ab1434c6

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-tinkoff-telephony-mock (version 35.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-tinkoff-telephony-mock across your stack and pipelines.
If you installed it — respond
bigops-tinkoff-telephony-mock is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-tinkoff-telephony-mock, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bigops-tinkoff-telephony-mock 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 bigops-tinkoff-telephony-mock 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. bigops-tinkoff-telephony-mock on npm has been identified as a malicious package (version 35.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015537GHSA-92wj-cj5h-gp6p

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-tinkoff-telephony-mock-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database