# Attackers compromised 42 GitHub repositories by using files too large to be searched

DevFeed: [Attackers compromised 42 GitHub repositories by using files too large to be searched](<https://devfeed.tech/articles/attackers-compromised-42-github-repositories-by-using-files-too-large-to-be-searched-102878.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4241474/attackers-compromised-42-github-repositories-by-using-files-too-large-to-be-searched.html>)

Author: Evan Schuman

Published: 2026-10-28T02:54:12Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Bun](<https://devfeed.tech/topics/bun.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [api](<https://devfeed.tech/tags/api.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-github-security-software-development-version-control-systems-vulnerabil](<https://devfeed.tech/tags/artificial-intelligence-github-security-software-development-version-control-systems-vulnerabil.md>), [attack](<https://devfeed.tech/tags/attack.md>), [breaches](<https://devfeed.tech/tags/breaches.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [ci](<https://devfeed.tech/tags/ci.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [file](<https://devfeed.tech/tags/file.md>), [files](<https://devfeed.tech/tags/files.md>), [github](<https://devfeed.tech/tags/github.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [large](<https://devfeed.tech/tags/large.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [version-control-systems](<https://devfeed.tech/tags/version-control-systems.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

## AI overview

JFrog reported compromises of 42 GitHub repositories, using wrappers up to 13.7 MB that evade ordinary GitHub search and API paths and decode to a shared CI publisher payload. Hooks for Claude, Gemini, Cursor, and VS Code can trigger when a developer opens a repository; a native addon decrypts `.napi_cache` at runtime. The campaign also involved hijacked accounts, forged commit timelines, exposed npm credentials, and malicious npm releases that stole credentials and propagated through repositories and package registries. JFrog recommends treating installation of a full-worm version as host compromise, rotating exposed credentials, auditing accessible repositories for unexpected tool hooks and execution files, enumerating repository trees directly instead of relying on code search or the contents API, removing unauthorized branches and workflows, and hunting relevant runner and network indicators. The excerpt links the activity to cPanel exploitation through Shellpanel artifacts; SafeDep described the npm payload as Miasma-family but noted uncertainty about lineage.

## Source excerpt

A security research firm reported Monday that it had identified breaches of 42 third-party GitHub repositories in which attackers had deployed payload blobs large enough "to evade the GitHub search and API paths normally used to find this kind of compromise." The report from JFrog Security Research said the victimized repositories contained execution hooks for AI coding assistants and IDEs, along with polymorphic wrappers as large as 13.7MB that "all decoded to the same hidden CI-publisher payload. The campaign's attacker-owned repository also operates as an active encrypted data sink, receiving snapshot envelopes, and the attack leveraged a new camouflage: a compiled native addon that contains no payload of its own, and instead decrypts a file named .napi_cache at runtime to reveal the real one." JFrog said that the investigation also uncovered account hijacks, forged commit timelines, short-lived publishing branches and exposed npm credentials. Shellpanel artifacts in the same hijacked owner cluster link this GitHub victim infrastructure to previously reported GitHub Actions exploitation of internet-facing cPanel systems. "During October 21 our scanners alerted us about shai-hulud packages found in the npm ecosystem," JFrog wrote. "SafeDep's October 22 analysis first documented the npm/package side of this activity and decoded event-bus-lite-testmetest@0.0.1. SafeDep described the payload as Miasma-family while explicitly noting uncertainty about its lineage." SafeDep had originally thought that the packages in the campaign it had discovered, dubbed testmetest, were merely a test by the threat actor, but this week discovered the compromises of existing repos with malicious content. The JFrog post also focused on the npm chain implications. "The npm chain provides the link into the broader operation. Malicious testmetest releases used a binding.gyp command expansion to execute index.js during installation, even though the packages did not declare a conventional ins