Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

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.

ShareXLinkedInHacker News
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

  1. 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.

  1. resolvedcritical

    Malicious code in epic-common-node (npm)

    The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.

    npmCompromised package
  2. containedcritical

    Malicious code in epic-common (npm)

    The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.

    npmCompromised package
  3. containedcritical

    Malware in leb128x

    The npm package leb128x was found to contain malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

    npmCompromised package
  4. containedcritical

    Malicious code in checkout-desktop-total (npm)

    The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.

    npmCompromised package