Today started quiet: SleeperGem's dormant-maintainer-account hijack on RubyGems was the only confirmed attack in six hours of monitoring, and the day looked headed for a light Monday.
Then, starting around 6pm ET, GitHub published 50 new advisories across a dozen ecosystems in a two-hour window, three of them critical. The sharpest supply-chain angle belongs to Composer, where a crafted transitive-package name can make Composer write files outside vendor/ during install, and to node-tar, whose decompression path can be driven into memory exhaustion by any tarball with no size cap — node-tar sits underneath npm, yarn, and pnpm's own extraction, so this reaches the install pipeline itself, not just direct importers. LightRAG picked up two criticals in the same window (a hardcoded default token secret and a CORS-wildcard-plus-credentials bug), and Mistune, Pillow, and Tornado each had their own multi-advisory clusters — nine, six, and three respectively — suggesting a coordinated audit push landed across several maintainers' desks at once.
Late addendum at 21:00 ET: the same wave hadn't actually stopped — it kept publishing for another ninety minutes past First Watch's snapshot, bringing tonight's GHSA total to 90. The second half added a duplicate-sized Pillow cluster (seven more heap-corruption and DoS bugs, mostly in image decoders and filters), seven more axios advisories (proxy and prototype-pollution edge cases, none RCE), nine Microsoft .NET CVEs across two NuGet packages (standard monthly patch-cycle noise), three more File Browser bugs, three more Guzzle cookie/header issues, and single entries for protobufjs and webpack-dev-server. None of it topped high severity, and nothing here is a confirmed active exploit — the ceiling for the day stays at the four criticals already on the board (SleeperGem, the two LightRAG bugs, and node-tar).
→ Operational priority for the night patch node-tar and Composer first given their reach into build and install tooling, then Pillow given it's now a thirteen-advisory cluster spanning loaders, filters, and encoders, then work down the rest of the high-severity list by internet exposure — Directus, Cloudreve, and changedetection.io's bugs are all reachable pre-auth if you expose them directly.