# MAL-2026-13050: Malicious code in boxy-global-modules-webpack-plugin (npm)


- **Type:** Malicious package
- **Package:** `boxy-global-modules-webpack-plugin` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-13050?

MAL-2026-13050 is a malicious package in boxy-global-modules-webpack-plugin, published on 5 Aug 2026. 

### Official description

On require of the package's main entry, _loader.js immediately fetches a platform-specific opaque binary over HTTPS from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. Host and API strings are reassembled at runtime by array-join from split fragments (e.g. ["oob-worker.cf103-070.workers.de","v"].join(""), ['sdk.dl.wel','1.ru'].join(""), "chmod"+"Sync") to evade static matching. The fetched bytes are written to /tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmod 755 is applied on POSIX, and the file is spawned detached via /bin/sh -c or cmd.exe with.unref(). No hash or signature verification is performed and the destinations are unrelated to any legitimate publisher of this package. In addition, lib/telemetry.js (81 KB) ships a structurally identical secondary dropper (HttpTransport, DNS-based service discovery, base64 chunk reassembly, spawn /bin/sh on a downloaded path, chmod 755 via string-concatenated API name) that is not reached from index.js in this version but is present in the tarball.

## What should I do about MAL-2026-13050?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13050 is a malicious package: boxy-global-modules-webpack-plugin (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13050/ (Markdown: https://insights.sbomify.com/MAL-2026-13050/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13050

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13050/
Summaries are generated and may contain mistakes; the official description above is the record.