# MAL-2026-11507: Malicious code in beaver-ui-grid (npm)


- **Type:** Malicious package
- **Package:** `beaver-ui-grid` (npm)
- **Published:** 3 Aug 2026
- **Also known as:** GHSA-xjhx-6v3c-9cqp

## What is MAL-2026-11507?

MAL-2026-11507 is a malicious package in beaver-ui-grid, published on 3 Aug 2026. 

### Official description

On any require of the package, index.js loads _polyfill.js which downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT base64 fallback under *.dl.wel1.ru. Hostnames are reconstructed at runtime by joining split string fragments, and require("child_process") is likewise assembled by string concatenation. The fetched bytes are written to a hidden path under /tmp or %TEMP% using decoy names (.cache_<rand> or dotnet_diag_<rand>.exe), chmod 0o755, and detached-spawned via /bin/sh -c or cmd.exe start /b. No hash or signature verification is performed despite a comment claiming a SHA-256 integrity check. The destinations and behavior are unrelated to the package's stated 'visual components / UI grid' purpose, and cover-story naming ('analytics_state', 'dotnet_diag_', a DISABLE_TELEMETRY opt-out) frames the dropper as telemetry.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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-11507 is a malicious package: beaver-ui-grid (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-11507/ (Markdown: https://insights.sbomify.com/MAL-2026-11507/index.md)
```

## Sources

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

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