Skip to content
42 GitHub Repositories Compromised via Large Payloads

42 GitHub Repositories Compromised via Large Payloads

First seen 28 Oct 2026, 06:49 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 28, 2026 at 07:49 UTC
  • •42 GitHub repositories compromised using large payloads to avoid detection.
  • •Attackers deployed polymorphic wrappers and a native addon to conceal malicious payloads.
  • •The attack is linked to previous exploitation of GitHub Actions and npm ecosystem vulnerabilities.

JFrog Security Research reported breaches of 42 third-party GitHub repositories, where attackers deployed large payload blobs to evade detection. The compromised repositories contained execution hooks for AI coding assistants and IDEs, with polymorphic wrappers up to 13.7MB that decoded to a hidden CI-publisher payload. The attackers used a compiled native addon that decrypts a file named .napi_cache at runtime to reveal the actual payload. Investigations revealed account hijacks, forged commit timelines, and exposed npm credentials. The attack is linked to previously reported GitHub Actions exploitation of internet-facing cPanel systems. The npm ecosystem was alerted to the presence of malicious packages named shai-hulud, with SafeDep documenting the npm/package side of the activity. The malicious releases aimed to steal GitHub and npm credentials, potentially compromising third-party repositories. The situation is ongoing, with further analysis required to fully understand the scope and impact.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-04-29
CVE-2026-41940 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-10-21
Scanners detect malicious npm packages
JFrog's scanners alerted the presence of shai-hulud packages in the npm ecosystem, indicating ongoing malicious activity.
Csoonline
2026-10-22
SafeDep analyzes npm/package activity
SafeDep documented the npm/package side of the activity and identified the payload as Miasma-family, noting uncertainty about its lineage.
Csoonline

More articles in this cluster (4)

Following this threat?

Track Miasma and CVE-2026-41940 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What types of repositories were affected?
The affected repositories included third-party GitHub repositories with execution hooks for AI coding assistants and IDEs.
How are attackers evading detection?
Attackers are using large payload blobs and a compiled native addon that decrypts malicious files at runtime to avoid detection.
What should organizations do to protect themselves?
Organizations should monitor their GitHub repositories for unauthorized changes and ensure their npm credentials are secure.