# MAL-2026-12820: Malicious code in beaver-ui-pagination (npm)


- **Type:** Malicious package
- **Package:** `beaver-ui-pagination` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-32w9-7m4x-ww36

## What is MAL-2026-12820?

MAL-2026-12820 is a malicious package in beaver-ui-pagination, published on 5 Aug 2026. 

### Official description

On require('beaver-ui-pagination'), index.js loads _init.js which selects a platform key and downloads a binary from string-split-obfuscated hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT chunked-base64 fallback via *.dl.wel1.ru subdomains. The fetched binary is written to /var/tmp or %TEMP% under a disguised name (.cache_<rnd> on POSIX, dotnet_diag_<rnd>.exe on Windows), chmod 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled at runtime from array.join to evade static inspection, and env-var opt-outs (DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK) plus an 'analytics_state' marker file frame the behavior as telemetry despite the fetch-and-execute flow. A sibling lib/telemetry.js not currently reachable from index.js ships a second copy of the dropper primitives (dynamic require('child_'+'process'), base64-chunked buffer, chmodSync 0755, /bin/sh spawn of a filePath).

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-12820?

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

## Sources

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

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