Technology & AI

Attackers hid payloads in 42 GitHub repositories

Intruders concealed malicious code in files of roughly 13 MB inside 42 GitHub projects, sized to slip past the platform's code search. Reports say the approach also bypassed search-based detection, putting customers' protections at risk.

By Standard Topic. AI-generated from the reporting listed under Coverage. Published . Updated .

This story is no longer being updated. It reflects reporting up to .

What happened

Attackers compromised 42 GitHub repositories by hiding a malicious payload in files measuring 12.9 to 13.7 MB. The files were large enough to evade GitHub code search.

Why it matters

The reports indicate that the attack got past search-based detection on GitHub. Customers' individual protections were compromised.

Timeline

  1. Oct 26, 6:29 PM ET: A worm was reported to have armed 42 GitHub repositories by hiding a payload too large to be searched.
  2. Oct 27, 10:54 PM ET: Reports said the security protections on GitHub were not breached, but individual customer protections were, with autonomous coding agents playing a role.

Coverage

More from Technology & AI

All Technology & AI news · Technology & AI story archive