Loading story…
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.
Trace attribution and downstream blast radius.
3 events from the most recent confirmed update back to the earliest known activity.
OpenSSF published guidance for maintainers on securing CI/CD pipelines in response to the tj-actions and reviewdog supply-chain attacks. The post reflects public acknowledgment of those incidents and recommended defensive measures.
OpenSSF and the OpenJS Foundation issued an alert about social-engineering attacks leading to takeovers of open-source projects. The alert marked a public warning to maintainers about this threat pattern.
Dragos published a report titled "ELECTRUM KAMASITE 10 Year Retrospective" covering activity targeting Poland's electric sector. The reference indicates the campaign and its historical analysis were publicly documented by this date.
See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
3 references tracked. Mallory keeps watching after this page renders.
openssf.org
Open sourceopenssf.org
Open sourcehub.dragos.com
Open sourceMap 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.
The Open Source Security Foundation warned that attackers are actively targeting open source developers, particularly Node.js and npm maintainers, with social engineering campaigns delivered through Slack, LinkedIn, Microsoft Teams, and fake Google Workspace pages. The activity mirrors the earlier compromise of an Axios maintainer, in which operators linked to North Korea allegedly used a fake Slack workspace, a cloned company identity, and a staged Teams call to trick the victim into installing a remote access trojan disguised as a software update, then used that access to push malware into npm packages with more than 100 million weekly downloads. New reports say the campaign now includes impersonation of a Linux Foundation community leader and malicious links sent into open source communities including ToDoGroup. OpenSSF said the fake Google Workspace flow is designed to steal credentials and verification codes and may prompt victims to install a fraudulent root certificate, enabling interception of encrypted traffic; Mac users may also receive an additional malicious binary that can lead to full system compromise. Security researchers and mailing list participants said the incidents highlight how attackers exploit trust on centralized collaboration platforms, and urged maintainers to verify identities through separate channels and treat any system, session, token, or credential exposed to the lures as compromised.
Jun 29, 2026
Software supply-chain compromise continued to blend into normal development activity, with attackers exploiting the speed and trust of modern workflows—third-party dependencies, automated updates, and rapid release cycles—to distribute malware and steal credentials. A ReversingLabs study covering 2025 open-source ecosystems reported **npm** as the dominant distribution channel for malicious packages, including incidents where attackers **compromised maintainer accounts** and shipped tainted updates that propagated quickly into downstream projects via routine dependency updates and CI/CD processes. One highlighted case was the **Shai-hulud** worm, described as a registry-native, self-propagating threat that used **stolen credentials** to inject malicious code into **hundreds of packages**, exposing **tens of thousands of downstream repositories** and complicating detection because it did not rely on external infrastructure. In parallel, commentary on generative AI’s impact on software delivery emphasized that faster code production and release pressure can increase security debt: reported industry claims that **20–30% of code** at major firms is AI-generated, alongside estimates that a large share of AI-generated code can introduce **OWASP Top 10**-class weaknesses, reinforcing the need for stronger testing and controls as development velocity increases.
Jun 29, 2026
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