tinkoff-terminal-kit-datetime
Affected
- Versions:
20.7.2
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in tinkoff-terminal-kit-datetime (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (3ff5d079ddd6e9ef6bd552f3a33ec5d0c87dcad3dce14013cbf28cbaa37a1dc1)
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.
Not rated by the source.
20.7.2None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0