Malicious code in tinkoff-boxy-mobile-vivid-heading (npm)
The npm package tinkoff-boxy-mobile-vivid-heading contained malicious code that fetches and executes arbitrary native binaries on package load. The malicious payload reconstructs Cloudflare Workers hostnames at runtime and uses DNS-TXT records as a fallback command-and-control channel to retrieve and execute opaque executables.
- Disclosed
- Last updated
- Blast radius
- Any developer or application that installed the malicious version of tinkoff-boxy-mobile-vivid-heading from npm.
- Ecosystems
- Attack vectors
- Affected entities
- tinkoff-boxy-mobile-vivid-headingnpm package containing malicious code
The npm package tinkoff-boxy-mobile-vivid-heading was found to contain malicious code in its runtime.js module. Upon package require, the code selects a platform-specific asset path and fetches an opaque binary over HTTPS from Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) whose names are reconstructed at runtime via string-fragment concatenation.\n\nThe package implements a DNS-TXT fallback channel that enumerates TXT records on tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site, base64-decoding concatenated chunks into an executable buffer. The fetched bytes are written to /var/tmp as a hidden dotfile on POSIX systems (or to %TEMP% as dotnet_diag*.exe on Windows), made executable with chmod 0755, and spawned detached via /bin/sh -c or cmd.exe with stdio ignored.\n\nA second module lib/telemetry.js contains an equivalent write+chmod+spawn+base64 chain under an 'Analytics SDK' cover story, though it is not reached from the entrypoint in the analyzed version. The stated 'device integration' purpose has no legitimate need for reconstructing destination hostnames from split fragments, shipping a DNS-TXT chunked binary loader, or fetching and executing opaque native binaries on load.\n\nThe malicious package was identified by the OpenSSF malicious-packages project and reported via GitHub Security Advisory GHSA-c49g-3j6g-ff99.", <parameter name="remediation">["Immediately uninstall tinkoff-boxy-mobile-vivid-heading from all projects and environments", "Audit npm package.lock or yarn.lock files to identify all installations of this package", "Review system logs and process execution history on any machines where this package was installed for signs of unauthorized binary execution", "Regenerate any credentials or secrets that may have been exposed on affected systems", "Update to a patched version if one is available, or replace the package with a legitimate alternative", "Implement npm package scanning and verification in your CI/CD pipeline to detect malicious packages before installation"]
Indicators of compromise
- Packages
- tinkoff-boxy-mobile-vivid-heading
- Domains
- oob-worker.cf100-416.workers.dev
- oob-worker.cf99-9b3.workers.dev
- oob-worker.cf103-070.workers.dev
- tin.dl.well1.site
- tina.dl.well1.site
- ldr.dl.well1.site
- win.dl.well1.site
Remediation
- Review the linked advisory; remove or upgrade the affected component and rotate any exposed credentials.
Sources
- GitHub Advisory GHSA-c49g-3j6g-ff99 · GitHub Advisory Database
Cite this entry
"Malicious code in tinkoff-boxy-mobile-vivid-heading (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-tinkoff-boxy-mobile-vivid-heading-npm-r87rcu
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package