Skip to content- Sources: primary, discussion
- Summary: BleepingComputer reports activity resuming on 2026-10-04 and reaching 17,610 repositories, with more than 13,000 pushed in 34 hours at a peak of 2,999 an hour, at least 700 of the accounts appearing to belong to legitimate developers, and Apiiro quoted saying 97 percent of sampled commits touched only the README while 88 percent pointed the Download button at a ZIP that installs SmartLoader, so the reported mechanism is reuse of a fleet that was already there rather than creation. Takedown is reported as structurally ineffective, because 71 percent of the fleet was missing from URLhaus before the report, copies persist in forks, older files, release assets and issue attachments, and a domain-level DNS blocklist cannot block one file on GitHub without blocking GitHub. The July wave, reported by Island at 7,600 repositories, included 800 posing as AI skills or MCP servers listed in public AI registries and catalogs, and the Apiiro report behind the current figures was not read on this run.
- Why it matters: The recommended response to suspected SmartLoader execution is to treat it as GitHub account compromise, revoke sessions and tokens and move to passkeys, and the repositories posing as AI skills or MCP servers in public registries reach anyone who installs agent tooling by following a README.
- Follow-up: The Apiiro report read directly, and whether the AI registry and catalog listings from the July wave are removed.