tinkoff-boxy-gitlab-labelsnpm
tinkoff-boxy-gitlab-labels is a confirmed malicious npm package (MAL-2026-12232) that executes malicious code on install (malicious version 20.5.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-boxy-gitlab-labels (npm)
What this malware does
On require of the package, index.js loads runtime.js which selects a platform-specific payload path, fetches an opaque native binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, cf101-adf, cf99-9b3, cf103-070.workers.dev) with a DNS-TXT chunked base64 fallback across hosts assembled from fragments (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site). The downloaded bytes are written to /tmp or %TEMP% under randomized names disguised as system tooling (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. Hostnames are reconstructed at runtime via Array.join to hide them from static inspection, and a silent stderr no-op is used to suppress logging. Behavior includes opt-out env checks, host shuffling, and a stamp file to run only periodically.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-boxy-gitlab-labels (version 20.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-boxy-gitlab-labels across your stack and pipelines.
If you installed it — respond
Remove tinkoff-boxy-gitlab-labels from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tinkoff-boxy-gitlab-labels 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-boxy-gitlab-labels 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tinkoff-boxy-gitlab-labels-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.