GitHub Advisory malware sweep, 10 November 2026

MediumAdvisory sweepnpmPyPI

270+ packages from GitHub malware advisories published 10 November 2026. Dominated by a Baileys WhatsApp library fork flood (~250 npm packages). Also: dependency-confusion probes targeting Telefonica, ING and Fidelity, CWE-506 boilerplate takedowns, and a PyPI Discord-webhook lure.

Published 10 Nov 2026

At a glancemulti-2026-11-10-ghsa-malware-sweep
113
Packages tracked125 malicious versions

Every version named by the advisory is in the scanner, so a lockfile check finds it directly.

Severity
Medium
Type
Advisory sweep
Published
10 Nov 2026
Ecosystems
npmPyPI
Detected by
OpenSSF, amazon-inspector

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.

What happened

The full picture

GitHub published malware advisories for over 270 packages on 10 November 2026. The vast majority are a coordinated flood of Baileys WhatsApp library forks. Severity is medium because no package in this sweep has a published analysis confirming a payload beyond the standard CWE-506 boilerplate.

The Baileys flood (Cluster A) published approximately 250 npm packages, all variations on the Baileys WhatsApp Web API library name. None had published analysis beyond the standard "treat host as fully compromised" takedown notice.

Ten scoped npm packages (Cluster B) appear to target internal registries at financial and telecom companies including PostEx, Telefonica, ING Bank, Futurae (an authentication provider), and Fidelity Investments (FMR). All are CWE-506 boilerplate with no confirmed payload.

The strutil-core RubyGems worm (GHSA-gv9w-h836-5f8g) also received its GitHub advisory today, but it is tracked in the named pystr-codec Miasma worm incident rather than this sweep.

dependency-confusiontyposquatobfuscation
Affected packages

113 packages 125 versions

These are usually pulled in as transitive dependencies rather than installed directly. Check your whole tree at once. It runs in your browser and nothing is uploaded.

Impact

What it does if you installed it

  • Cluster A: Baileys WhatsApp library fork flood (malicious-package; CWE-506 boilerplate, no published analysis) (~250 npm packages): Massive burst of packages with names containing "baileys", "bail", or related strings (e.g. zenvy-baileys, turbo-baileys, @baileys-md/baileys, @hanzzyy/baileys). All received standard CWE-506 takedown notices with no published analysis of the payload. Representative GHSA IDs: GHSA-xcrr-68m7-3c73, GHSA-6wxx-wg3c-9j4r, GHSA-fmcg-cw36-2rvf. See the full package list below.
  • Cluster B: npm dependency-confusion probes (dependency-confusion; CWE-506 boilerplate, no payload beyond beacon) (10 packages): @postex/common, @jm-telefonica/multibrand-components, @generic-means/ing-feat-scanner-libs, @futurae-public/adaptive-js, @fmr-ap149494/apex-base-component, @fmr-ap153177/apex-kit-icons, @fcsmc/commercial-analytics, @factoryz/apollo, @openyard/vetcode, @conduitops/logview-archive. Scoped names suggest internal registries at PostEx, Telefonica, ING Bank, Futurae, Fidelity (FMR). All CWE-506 boilerplate with no published analysis.
  • Cluster C: npm CWE-506 boilerplate takedowns (malicious-package; no published analysis) (20+ packages): kube-health-tools (13 versions), npm-scanner, nodecheck-health, moltbook-health, moltbook-api-helper, leveldb-edit, and 7 dowload_ebok_* ebook-spam lure packages. All received standard takedown notices.
  • Cluster D: PyPI shanks Discord-webhook lure (malicious-package; published analysis) (1 package): shanks 0.0.4. On import, queries a geolocation service for the host IP and posts IP, city, state, coordinates to a hard-coded Discord webhook. Low-severity lure. MAL-2026-19051.
  • Note: RubyGems strutil-core 1.0.1 (GHSA-gv9w-h836-5f8g, MAL-2026-19054), a Miasma-family worm, also received its GHSA advisory on Nov 10. It is tracked in the named incident pystr-codec Miasma worm.
What to do

Clean-up steps

  1. Check your lockfiles for every package and version listed below, or upload them to the DependencyWatch scanner
  2. Baileys forks (Cluster A): if any of these appeared in your lockfile, remove them and rebuild; rotate secrets if the host executed the package
  3. Dep-confusion probes (Cluster B): uninstall; if installed in CI, review whether internal package or scope names leaked; consider configuring a scoped registry for your organization
  4. CWE-506 boilerplate (Cluster C): remove and rebuild; rotate secrets if the host ran the package
  5. shanks (Cluster D): remove; low-severity, no credential theft beyond IP geolocation
References

Sources

multi-2026-11-10-ghsa-malware-sweepBack to incidentsSubmit a correction
Am I affected?

Check your lockfile against this and every other incident.

Paste a lockfile and it is matched on your own device against every compromised version we track. Nothing is uploaded and there is no account.