Get paid to wait
The Claude Code spinner might be the most watched line on Earth.
So I turned it into an ad marketplace.
Advertisers bid on it. You keep 50% of the money.
Install the extension โ get cash from ads.
Introducing Kickbacks
๐จ Breaking: 31 npm packages from @RedHat have been compromised.
100,000+ weekly downloads affected. The upstream CI/CD pipeline was compromised, with all packages published via GitHub Actions OIDC.
The payload:
โ ๏ธ Reads GitHub Actions runner process memory to extract masked secrets
โ ๏ธ Sweeps credentials across AWS, GCP, Azure, K8s, Vault, and npm
โ ๏ธ Self-propagating worm that republishes backdoored packages using stolen npm tokens, bypassing 2FA
โ ๏ธ Persists on dev machines via Claude Code settings hijack and VS Code task injection
โ ๏ธ Exfiltrates data through GitHub API commits, blending in with normal git operations
We have responsibly disclosed the incident to the maintainers.
Full technical analysis: https://t.co/63nZYH1cMO
Liftoff of Starship V3, from the dunes right outside the pad.
This is the most insane shockwave action I have ever seen on video. Absolutely mad.
๐ฝ๏ธ Me for @WeAreSpaceScout
โผ๏ธ๐จ BREAKING: Another supply chain attack. 700+ GitHub repositories flagged, including PHP and Node.js projects. The malicious script was planted across all of them. When a developer installs the package, the script silently downloads a Linux file from GitHub, hides it under the name /tmp/.sshd (so it looks like a normal system file), and runs it in the background. It also skips security checks on the download and hides any error messages.
8 PHP packages on Packagist (the main PHP code library) were confirmed infected. The attacker hid the script inside a JavaScript config file (package.json) instead of the PHP one (composer.json), so PHP developers reviewing their code would not notice it. The biggest risk is to devdojo/wave (6,400 stars) and devdojo/genesis (9,100 installs), both popular Laravel project templates. Developers who use these templates run the bad script the moment they install dependencies.
The same payload was also dropped into GitHub Actions (automated build pipelines) under a fake step called "Dependency Cache Sync," meaning it could infect company build servers too. Packagist removed the bad packages, but the auto-updating versions (dev-main, dev-master, 3.x-dev) can quietly come back if the original repos stay infected.
IOCs:
GitHub account parikhpreyash4
repo systemd-network-helper-aa5c751f
drop path /tmp/.sshd
command fragments curl -skL and chmod +x /tmp/.sshd.
UPDATE: So far we've identified 639 compromised npm package versions across 323 unique packages in tonightโs Mini Shai-Hulud wave.
That includes 558 versions across 279 unique @โantv packages. Most were detected within ~6 minutes of publication.
https://t.co/JXJK1NT4dp
@okorojames_@modat_magnify They definitely audit. It's just that new tools are catching deep, legacy flaws like React2shell that stayed hidden for years. Frequent patches are a sign of way deeper scrutiny, not worse code. Weโre basically just seeing a long-overdue deep clean of the ecosystem
โผ๏ธ๐จ UPDATE: The TanStack npm attack is now a full campaign.
'Mini' Shai-Hulud has hit:
- OpenSearch
- Mistral AI
- Guardrails AI
-UiPath
- Squawk packages across npm and PyPI
The malware specifically targets AI developer tooling. It hooks into Claude Code (.claude/settings.json) and VS Code (.vscode/tasks.json) to re-execute on every tool event, long after the infected package is gone. npm uninstall does not fix this.