# GitHub Advisory malware sweep, 2 November 2026

> 6 packages from GitHub malware advisories published between 06:00 UTC on 1 November and 06:00 UTC on 2 November 2026: two Baileys WhatsApp forks with an unpinned off-registry dependency, one out-of-band DNS probe and three CWE-506 takedowns. No confirmed payload beyond probes.

- Published: 2026-11-02
- Last updated: 2026-11-06
- Severity: medium
- Kind: Advisory sweep - A dated batch of GitHub Advisory Database malware entries collected together. A sweep mixes kinds - typosquats, dependency-confusion probes, boilerplate takedowns with no published analysis, and occasionally real payloads - and its severity reflects the worst confirmed item, not the batch as a whole.
- Ecosystems: npm, RubyGems
- Scope: 6 packages, 7 compromised versions
- Tags: dependency-confusion
- Also known as: GHSA 2026-11-02 batch
- Detected by: GitHub Advisory Database, OpenSSF Package Analysis, Amazon Inspector
- Incident ID: multi-2026-11-02-ghsa-malware-sweep

## Affected packages (6)

Only the exact versions listed were named by the source advisories. Other versions are not implicated.

| Package | Ecosystem | Compromised versions |
|---|---|---|
| [@an1mshnpmb9c84920/pipeprobe-obf-m19n5](https://dependencywatch.io/package/npm/@an1mshnpmb9c84920/pipeprobe-obf-m19n5) | npm | 1.0.0 |
| [@axo_cuy/baileys](https://dependencywatch.io/package/npm/@axo_cuy/baileys) | npm | 1.0.0 |
| [@bil-rgb/baileys](https://dependencywatch.io/package/npm/@bil-rgb/baileys) | npm | 1.0.0, 1.0.1 |
| [atlassian-wallboard-plugin](https://dependencywatch.io/package/npm/atlassian-wallboard-plugin) | npm | * |
| [dsh-screenshot-native](https://dependencywatch.io/package/npm/dsh-screenshot-native) | npm | 1.0.0 |
| [macs-shoaibs-pro17](https://dependencywatch.io/package/rubygems/macs-shoaibs-pro17) | RubyGems | 90002.1 |

## What happened

GitHub published malware advisories for 6 packages in this window (npm and RubyGems). It is a quiet day: the only analysed items are two Baileys forks with an unpinned dependency and a DNS callback probe.

## Indicators named in the advisories

- `npmp19n5--768.oob.awss.dev` (out-of-band probe callback)

Severity is `medium` because nothing in the batch has a confirmed payload beyond a beacon.

## Impact

- **Cluster: trojanised Baileys WhatsApp library forks (malicious-package; advisory analysis published) (2 packages)**: `@axo_cuy/baileys`, `@bil-rgb/baileys`. Forks of the Baileys WhatsApp Web library that pull their `libsignal` dependency straight from a personal GitHub repository with no pinned commit, so whoever controls that repository decides what runs on install. Use the official `@whiskeysockets/baileys` only.
- **Cluster: dependency-confusion and pentest probes (dependency-confusion; beacon only) (1 package)**: `@an1mshnpmb9c84920/pipeprobe-obf-m19n5`. These send only host details (hostname, username, working directory) to a callback host, mostly under internal-looking or squatted names at inflated versions. No payload beyond the beacon was reported, but a hit means your build resolved a public package where you expected a private one.
- **Cluster: CWE-506 takedowns with no published analysis (malicious-package; likely probes or lures) (3 packages)**: `atlassian-wallboard-plugin`, `dsh-screenshot-native`, `macs-shoaibs-pro17`. GitHub published only its standard "treat the host as compromised" notice for these, with no payload analysis.

## What to do

1. **Check your lockfiles** - search `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `requirements*.txt`, `poetry.lock`, `uv.lock` and `Gemfile.lock` for every package and version listed below, or upload them to the DependencyWatch scanner
2. **Probes and spam** - remove the package, rebuild, and check whether your registry configuration lets public packages shadow internal or scoped names
3. **Egress** - DNS lookups to `*.oob.awss.dev` from build hosts indicate a probe ran

## Check your own dependencies

- Check a package-lock.json against this incident: https://dependencywatch.io/check/package-lock-json

The scan runs entirely in the browser; lockfile contents are never uploaded.

## References

- [GitHub Advisory Database, malware advisories](https://github.com/advisories?query=type%3Amalware&sort=published-desc) - GitHub
- [OpenSSF malicious-packages repository](https://github.com/ossf/malicious-packages) - OpenSSF
- [GHSA-9xq2-7mfg-rrmx - npm @bil-rgb/baileys](https://github.com/advisories/GHSA-9xq2-7mfg-rrmx) - GitHub
- [GHSA-xq83-5ggr-7222 - npm pipeprobe out-of-band DNS probe](https://github.com/advisories/GHSA-xq83-5ggr-7222) - GitHub
- [GHSA-vj43-6r45-847h - npm atlassian-wallboard-plugin](https://github.com/advisories/GHSA-vj43-6r45-847h) - GitHub
- [DependencyWatch: previous day's sweep](https://dependencywatch.io/incident/multi-2026-11-01-ghsa-malware-sweep)

---

Canonical page: https://dependencywatch.io/incident/multi-2026-11-02-ghsa-malware-sweep
Markdown version: https://dependencywatch.io/incident/multi-2026-11-02-ghsa-malware-sweep.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).