Loading story…
Recent developments in open source supply chain security have introduced enhanced monitoring and detection capabilities for package maintainers and developers. Trail of Bits is preparing Sigstore’s rekor-monitor for production, enabling developers to detect tampering and unauthorized use of their identities in the Rekor transparency log. This tool, funded by the OpenSSF, supports the new Rekor v2 log, certificate validation, and integration with The Update Framework (TUF), allowing maintainers to monitor for unexpected signing events and quickly identify potential compromises in their release process. Transparency logs like Rekor provide append-only, tamper-evident records, but require active monitoring to ensure trustworthiness, especially in the event of compromised identities.
Simultaneously, Deno 2.6 has introduced new supply chain security features, including a deno audit command that scans dependencies against GitHub's CVE database and integrates with Socket's Firewall API for real-time detection of malicious packages and supply chain risks. The Socket integration allows both unauthenticated and authenticated scanning modes, providing instant security scanning and the ability to enforce organizational security policies. These advancements reflect a broader trend toward proactive, behavior-based detection of supply chain threats, moving beyond traditional CVE-based vulnerability scanning to catch emerging risks such as typosquatting, malicious install scripts, and obfuscated code before they impact production environments.
See real exploitation activity before you spend the cycle.
4 events from the most recent confirmed update back to the earliest known activity.
Deno 2.6 added integration with Socket's Firewall API to provide real-time supply-chain threat detection from the CLI. The integration supports both unauthenticated and authenticated scanning modes so organizations can enforce security policies and get detailed threat analysis.
Deno 2.6 introduced a new 'deno audit' command to scan dependencies against GitHub's CVE database. The release also added granular script approval, minimum dependency age requirements, and faster typechecking via tsgo.
Trail of Bits reported improvements to rekor-monitor including support for the new Rekor v2 log, certificate validation, enhanced reliability, and integration with The Update Framework. The project also added a reusable GitHub workflow to make transparency-log monitoring easier to adopt.
OpenSSF funded work to prepare Sigstore's rekor-monitor for production use so package maintainers can detect tampering and unauthorized use of their identities in the Rekor transparency log. The effort included contributions from Sigstore maintainers as part of broader open source supply-chain security work.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Open-source software supply chain risk continued to escalate, with reporting citing **454,600+** newly identified malicious packages across major repositories (including **PyPI, npm, Maven Central, NuGet, and Hugging Face**) and tactics ranging from **credential theft** to **multi-stage attacks** and even early **self-replicating** package malware. The activity reportedly concentrated heavily in **npm**, including high-volume “ecosystem flooding” (e.g., single accounts publishing **150,000+** malicious packages in days) and **hijacking of trusted projects**, exploiting developer reliance on superficial trust signals such as package names, READMEs, and download counts. Separately, researchers disclosed **“PackageGate”** vulnerabilities in JavaScript package managers (**npm, pnpm, vlt, and Bun**) that can bypass common post-incident defenses—namely `--ignore-scripts` and lockfile integrity—enabling malicious code execution via compromised dependencies. Koi Security reported six issues; **pnpm, vlt, and Bun** shipped fixes, while **npm** reportedly treated the behavior as expected. In parallel, threat actors abused **GitHub’s fork architecture** to distribute a spoofed *GitHub Desktop* installer promoted via search ads; execution deployed **HijackLoader** and established persistence via a **scheduled task**, underscoring that supply chain threats extend beyond package registries into developer tooling distribution channels.
Jun 29, 2026
Security researchers have identified a significant increase in destructive malware embedded within open source packages across major ecosystems such as npm, PyPI, NuGet, Go modules, and Docker Hub. Unlike financially motivated threats like cryptominers or credential stealers, these malicious packages are designed to inflict operational damage by deleting source code, wiping repositories, breaking builds, or sabotaging developer environments. Attackers often disguise these packages as legitimate developer tools or utilities, leveraging trusted registries to maximize reach and impact. The destructive payloads are frequently delayed or remotely controlled, allowing threat actors to time their attacks for maximum disruption while evading early detection. In CI/CD environments, a single compromised dependency can propagate rapidly, amplifying the operational fallout before the threat is identified and contained. Recent research highlights that Docker Hub, a widely used container registry, has also become a vector for supply-chain attacks, with malicious images distributed at scale to facilitate cryptomining and potentially more destructive activities. These campaigns exploit the implicit trust developers and organizations place in public registries, as well as the automated nature of modern software pipelines. Security teams are urged to extend supply-chain security controls beyond source code to include container images and other artifacts, as attackers continue to innovate in their methods for infiltrating and sabotaging software development and deployment workflows.
Jun 29, 2026
The Open Source Security Foundation and the OpenJS Foundation issued an alert warning that attackers are using social engineering to seize control of open-source projects by targeting maintainers and trusted contributors. The warning highlighted account takeovers, fraudulent outreach, and other tactics that can give adversaries the ability to publish malicious updates through legitimate projects, creating downstream risk for organizations that depend on widely used packages and developer tooling. OpenSSF later published guidance for maintainers on hardening CI/CD pipelines after the `tj-actions` and `reviewdog` supply-chain incidents, emphasizing stronger identity verification, tighter repository and workflow permissions, protection for release processes, and closer monitoring of automation used to build and distribute software. Together, the alerts describe a growing pattern in which attackers compromise trust in the open-source ecosystem and then abuse build and release infrastructure to propagate malicious code to users at scale.
Jul 12, 2026