boxy-get-retry-urlnpm
boxy-get-retry-url is a confirmed malicious npm package (MAL-2026-13049) that executes malicious code on install (malicious version 35.4.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-get-retry-url (npm)
What this malware does
On require, index.js delegates to helpers.js which selects a platform-specific asset path, downloads an opaque binary over HTTPS from obfuscated Cloudflare Workers subdomains (hostnames like 'oob-worker.cf102-baf.workers.dev' are reassembled at runtime from split string arrays), writes it to a disguised path under /tmp or %TEMP% (filenames like 'dotnet_diag.exe', '.cache_', 'package-arm64', 'loader_mac'), chmods 0755 on Unix, and spawns it detached via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}) with stdio ignored. A secondary DNS-TXT covert channel queries 'c.<domain>' at *.dl.wel1.ru for a chunk count, retrieves N base64 chunks via resolveTxt, concatenates them into a buffer, and feeds the same write+exec sink. No hash or signature verification is performed and the destinations are unrelated to any legitimate publisher. Endpoint hostnames are assembled from fragmented arrays joined with '' to evade static detection.
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 boxy-get-retry-url (version 35.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-get-retry-url across your stack and pipelines.
If you installed it — respond
Remove boxy-get-retry-url 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 boxy-get-retry-url 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 boxy-get-retry-url 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 boxy-get-retry-url-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.