Which versions of tinkoff-volna-zustate are malicious?

The following npm versions of tinkoff-volna-zustate are flagged malicious: 20.9.2. Treat any of these as compromised.

How do I remediate tinkoff-volna-zustate if I installed it?

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

I already installed tinkoff-volna-zustate — how do I know if it already compromised me?

If tinkoff-volna-zustate 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-volna-zustate part of a known attack campaign?

Yes — tinkoff-volna-zustate is associated with the IN-MAL-2026-014518 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-volna-zustate 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-volna-zustate (version 20.9.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-volna-zustate across your stack and pipelines.

Malicious package

tinkoff-volna-zustatenpm

tinkoff-volna-zustate is a confirmed malicious npm package (MAL-2026-12284) that typosquats a legitimate package to trick installs (malicious version 20.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-volna-zustate (npm)

MAL-2026-12284

Immediate action

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

npm uninstall tinkoff-volna-zustate

What this malware does

On require('tinkoff-volna-zustate'), index.js loads bridge.js which downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev), with a DNS-TXT covert-channel fallback that reassembles base64 chunks from subdomains under dl.well1.site. The fetched payload is written to /var/tmp/.cache<rnd> or %TEMP%/dotnet_diag_<rnd>.exe, chmod 0755, and executed detached via /bin/sh -c or cmd.exe /c start. Destination hostnames are assembled from split string fragments via.join("") to evade static string scanning. Package name and description impersonate the Tinkoff brand ('Internal tinkoff volna zustate module for platform services') to encourage dependency-confusion installs. Import-time execution of attacker-controlled bytes against the installer's host with disguised filenames, hidden staging paths, obfuscated destinations, and a DNS-TXT fallback channel is the fingerprint of a supply-chain dropper.

Malicious versions

1 flagged

20.9.2

Indicators of compromise (SHA-256)

01865b8f060a3e4a24f34537d14ace960460519b2e5e3073083c7de9da63bd9e

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 tinkoff-volna-zustate (version 20.9.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-volna-zustate across your stack and pipelines.
If you installed it — respond
tinkoff-volna-zustate is a typosquat — you almost certainly intended a legitimately-named package. Remove tinkoff-volna-zustate, 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 tinkoff-volna-zustate 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-volna-zustate 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-volna-zustate on npm has been identified as a malicious package (version 20.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014518

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-volna-zustate-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