CVE
CVE-2026-73416, CVE-2026-73627, CVE-2026-73626
CWE
CWE-178, CWE-180, CWE-295, CWE-494, CWE-506, CWE-522
Affected Surface
- Ruby developer workstations that installed the 15-16 August StubMaker typosquat gems and triggered `extconf.rb` during installation
- Teams still assessing the downstream credential exposure from the malicious `litellm` PyPI releases `1.82.7` and `1.82.8`
- JupyterLab and Notebook v7+ deployments that expose the PyPI Extension Manager and rely on blocklists or plugin locks as hardening controls
Welcome to Corgea’s weekly briefing. The briefing covers the most important security findings and research from the week.
This edition covers research published from Wednesday, 12 August through Tuesday, 18 August 2026, excluding items already covered in the 11 August briefing.
Top Article
StubMaker: RubyGems extconf.rb typosquats delivered a Windows infostealer
This week’s most important story is StubMaker because it shows a package ecosystem feature becoming the exploit path. The fresh technical point is not only that brumdler and brundlef were typosquats of bundler. It is that the malicious gems abused extconf.rb to run code during the native-extension phase, manufactured empty build artifacts so installation still looked normal, and then pulled a Windows-focused loader chain that unpacked a larger in-memory stealer without needing a second obvious payload URL.
That puts StubMaker beside SleeperGem, AsyncAPI’s require-time compromise, and the broader ChainDrop keyv / cacheable worm. The shared AppSec lesson is that the dangerous step is no longer only “did a package install script run.” It is “what code path did the package manager, language runtime, or developer tool agree to execute as part of a normal workflow.”
More news
LiteLLM’s March PyPI compromise maps to 434,000 CI/CD pipelines
The August 11-14 LiteLLM follow-on reporting matters because it finally put rough blast-radius numbers behind a compromise we already knew was serious. The key point for defenders is to separate the directly malicious artifacts, litellm==1.82.7 and 1.82.8, from the much larger reconstructed exposure set. CloudSEK and the follow-on coverage are describing a broad credential-exposure event tied to the TeamPCP wave, not proof that every named organization directly installed LiteLLM itself. Even with that nuance, the incident is still a strong reminder that short-lived malicious package windows can leave long-lived credential response work behind.
CVE-2026-73416 and CVE-2026-73627: JupyterLab extension-manager bypasses
JupyterLab is the week’s most important package-governance story because the bug class sits exactly where many platform teams think policy already exists. The extension manager could mis-handle administrator intent in three ways: blocklists compared non-canonical names, plugin-lock enforcement was incomplete in /lab/api/plugins, and one install path skipped its own allowlist gate because of a missing await. This is less cinematic than supply-chain malware, but it is still the kind of package-policy failure that matters in shared notebook and JupyterHub deployments.
From research to remediation
Check whether this pattern exists in your codebase
Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.