DependencyWatch.io
Talk to PrecursorScan a lockfile

GitHub Advisory malware sweep, 9 November 2026

HighAdvisory sweepnpmPyPIRubyGems

19 packages from GitHub malware advisories published 8–9 November 2026 (after the previous sweep cutoff). Headlines: PyPI chromacli infostealer campaign, RubyGems oastify.com pentest beacons, PyPI infostealer droppers, and dependency-confusion probes.

Published 9 Nov 2026

Check your package-lock.jsonSource advisory
At a glancemulti-2026-11-09-ghsa-malware-sweep
19
Packages tracked23 malicious versions

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

Severity
High
Type
Advisory sweep
Published
9 Nov 2026
Ecosystems
npmPyPIRubyGems
Detected by
OpenSSF, kam193, 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 19 packages between 8 November 2026 (after the previous sweep cutoff) and 9 November 2026. Severity is high for the confirmed infostealer campaigns.

The chromacli campaign (Cluster A) published four PyPI packages that download and execute infostealer binaries. The rainbowcolors variant targets Windows specifically, adding Defender exclusions before dropping solace.exe from gofile.io. The campaign was flagged by kam193 via OpenSSF.

Four RubyGems (Cluster B) all follow the same Burp Collaborator beacon pattern: each ships a fake native extension that collects system info and sends it to oastify.com. These are likely pentest or bug-bounty probes with no confirmed malicious payload beyond reconnaissance.

The @ethersphere/bee-js 13.3.0 compromise, also published 9 November, is tracked in its own named incident.

infostealerdependency-confusiontyposquatobfuscation
Affected packages

19 packages 23 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.

Check package-lock.json →Check requirements.txt →
Impact

What it does if you installed it

  • Cluster A: PyPI chromacli infostealer campaign (malicious-package; published analysis) (4 packages): chromacli, super-color, supercolor-tui, rainbowcolors. Part of the 2026-11-chromacli campaign reported by kam193. Each downloads and executes an infostealer binary. rainbowcolors specifically targets Windows, adding Defender exclusions before dropping its payload. super-color and supercolor-tui use the same loader pattern.
  • Cluster B: RubyGems oastify.com reconnaissance beacons (dependency-confusion; beacon only, no payload beyond system info) (4 packages): control-character-command-injection, donjon-ledger, dynamic-object-handler, agentic-call-control. Each gem runs an extension script on install that collects hostname, username, and /etc/passwd and sends the data over TLS to oastify.com (Burp Collaborator). Likely pentest or bug-bounty probes.
  • Cluster C: PyPI dependency-confusion probes (dependency-confusion; beacon only) (3 packages): expect-tests, infra-libs, blender-headless. Each exfiltrates hostname via DNS subdomain encoding. expect-tests uses sentinel version 99.99.99, typical of internal-name squatting.
  • Cluster D: PyPI infostealer droppers (malicious-package; published analysis) (3 packages): bundyfed, extrahtml, parseyaml. Each overrides the install command to download and execute a remote infostealer binary. parseyaml and extrahtml masquerade as YAML/HTML utilities.
  • Cluster E: npm/PyPI CWE-506 boilerplate takedowns (no published analysis) (5 packages): lookuptest11, @htooayelwinict/travis234, internal-company-module-test-1337, kafbail, seolibs-package. GitHub published only its standard "treat the host as compromised" notice.
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. Infostealers (Clusters A, D): uninstall, isolate the host, rotate every credential, check for persistence mechanisms
  3. Pentest beacons (Cluster B): uninstall; if installed in CI, review whether internal hostnames leaked
  4. Dep-confusion probes (Cluster C): uninstall; if installed only in CI, review whether internal package names leaked
  5. CWE-506 boilerplate (Cluster E): remove the package and rebuild; rotate secrets if the host ran the package
References

Sources

multi-2026-11-09-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.

Check your package-lock.jsonAll incidents