Which versions of tinkoff-terminal-kit-datetime are malicious?

The following npm versions of tinkoff-terminal-kit-datetime are flagged malicious: 20.7.2. Treat any of these as compromised.

How do I remediate tinkoff-terminal-kit-datetime if I installed it?

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

I already installed tinkoff-terminal-kit-datetime — how do I know if it already compromised me?

If tinkoff-terminal-kit-datetime 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-terminal-kit-datetime part of a known attack campaign?

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

Malicious package

tinkoff-terminal-kit-datetimenpm

tinkoff-terminal-kit-datetime is a confirmed malicious npm package (MAL-2026-12280) that typosquats a legitimate package to trick installs (malicious version 20.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tinkoff-terminal-kit-datetime (npm)

MAL-2026-12280

Immediate action

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

npm uninstall tinkoff-terminal-kit-datetime

What this malware does

The package's main index.js unconditionally requires runtime.js, which on any require/import selects a platform-specific endpoint and downloads an opaque binary over HTTPS from author-controlled Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT chunked-base64 fallback via tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The destination hostnames are assembled from split string fragments (e.g. "oob-worker.cf100-416.wor"+"ke"+"rs.de"+"v") and require is accessed indirectly (require("child"+"process")) to defeat static analysis. The downloaded bytes are written to /tmp or %TEMP% under a disguised name (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe with unref(). There is no version pinning, no hash or signature verification, and the package's declared purpose is a datetime library with no legitimate need for a native binary. A sibling lib/telemetry.js repeats the same child_process + base64 + chmod 755 pattern. The name resembles a Tinkoff-adjacent scope, consistent with a typosquat lure delivering an opaque second-stage payload.

Malicious versions

1 flagged

20.7.2

Indicators of compromise (SHA-256)

3ff5d079ddd6e9ef6bd552f3a33ec5d0c87dcad3dce14013cbf28cbaa37a1dc1

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

Campaign

IN-MAL-2026-014495

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tinkoff-terminal-kit-datetime-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