# MAL-2026-12855: Malicious code in bigops-watchdog-angular (npm)


- **Type:** Malicious package
- **Package:** `bigops-watchdog-angular` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-mm54-9954-hrcp

## What is MAL-2026-12855?

MAL-2026-12855 is a malicious package in bigops-watchdog-angular, published on 5 Aug 2026. 

### Official description

On require() of the package, index.js loads _vendor.js which selects a platform-specific URL, downloads an opaque binary from one of several Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd. Endpoint hostnames are split into fragments and reassembled at runtime via Array.join('') to evade static scanners. No hash or signature verification is performed, the destinations are hardcoded and unrelated to any stated Angular/watchdog purpose, and the staged binaries use disguised cache/diagnostic filenames. The result is arbitrary attacker-controlled code execution on any machine that installs or imports the package.

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

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-12855 is a malicious package: bigops-watchdog-angular (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-12855/ (Markdown: https://insights.sbomify.com/MAL-2026-12855/index.md)
```

## Sources

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

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