Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

boxy-make-tokens-mapnpm

boxy-make-tokens-map is a confirmed malicious npm package (MAL-2026-13056) that steals credentials and exfiltrates sensitive data (malicious version 35.9.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-make-tokens-map (npm)

MAL-2026-13056
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall boxy-make-tokens-map

What this malware does

index.js unconditionally requires./loader on module load. loader.js reconstructs three Cloudflare Worker hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) via array-join string obfuscation, selects a platform-specific path, downloads an executable over HTTPS, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag<hex>.exe on Windows (a decoy filename impersonating a Microsoft diagnostic tool), chmods it 0755, and spawns it detached and unref'd via /bin/sh or cmd. A DNS-TXT channel under *.dl.wel1.ru (hostnames such as sdk.dl.wel1.ru also reassembled via.join('')) reconstructs a base64-encoded payload from numbered subdomains as an out-of-band delivery/fallback channel. A marker file at /tmp/.analytics_state (or %TEMP%\analytics_state) with a TTL rate-limits re-execution. The stated purpose ('token map') does not match any of the observed behavior, and 'telemetry'/'analytics' comments provide cover-story framing.

Malicious versions

1 flagged
35.9.7

Indicators of compromise (SHA-256)

a3b24115f2a42bc7aa25741e66f56e8007a3d0816cab809e1da78740f9a7a2d5

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-make-tokens-map (version 35.9.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-make-tokens-map across your stack and pipelines.

  2. If you installed it — respond

    boxy-make-tokens-map is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If boxy-make-tokens-map 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.

  4. How O3 protects you

    O3 blocks boxy-make-tokens-map 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

No. boxy-make-tokens-map on npm has been identified as a malicious package (version 35.9.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015321

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks boxy-make-tokens-map-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
boxy-make-tokens-map (npm) malicious package — MAL-2026-13056 | O3 Security