tinkoff-boxy-mobile-separator
This report shows the evidence for tinkoff-boxy-mobile-separator@20.8.8. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12235 confirms this npm version as malicious.
Advisory
MAL-2026-12235
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in tinkoff-boxy-mobile-separator (npm)
Details
On require() of tinkoff-boxy-mobile-separator, index.js loads _init.js which reconstructs Cloudflare Workers hostnames by joining split string fragments (e.g. ['oob-worker.cf101-adf.worker','s.','de','v'].join('')), downloads a platform-specific opaque binary via https.get, writes it to /var/tmp or %TEMP% under a randomized hidden name (dotnet_diag_*), chmods it 0755, and spawns it detached via spawn('/bin/sh',['-c',fp+' &']) or spawn('cmd',...). A DNS-TXT covert channel (c.<domain> for chunk count, N.<domain> for base64-encoded chunks reassembled with Buffer.from(parts.join(''),'base64')) provides a fallback payload retrieval mechanism. No hash or signature verification is performed on the fetched executable. A second, structurally identical dropper is bundled at lib/telemetry.js (not reached from the main require graph but present in the tarball). The package name impersonates the Tinkoff namespace; there is no legitimate SDK behavior in the shipped code.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to tinkoff-boxy-mobile-separator@20.8.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing tinkoff-boxy-mobile-separator@20.8.8. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.