
TeamPCP stole about 3,800 GitHub repos via poisoned developer tools
GitHub says customer-owned repositories were not accessed, but some stolen internal repos held customer support excerpts.
55 stories, newest first · one card per story

GitHub says customer-owned repositories were not accessed, but some stolen internal repos held customer support excerpts.

PHP fixes shipped October 21; nine firms, including ESET, told NBC News they had seen no successful PHP2Shell attacks.

GitLab’s unauthenticated RCE is CVSS 10.0 back to version 7.0; LiteLLM 1.107.0 stole credentials and OpenCode keys may have leaked.
Poisoned release 1.107.0 carried an infostealer and remote access trojan and drew about 49,000 downloads before PyPI quarantined it.
The Hacker News listing only shows a link to github.com/usestrix/firewall, with 22 points and one comment.

The October 26 bulletin also flags an exploited Arista flaw, a LiteLLM package compromise, and the Aokigahara infostealer.

CISA listed four exploited Plex flaws, while a leaked LiteLLM key led to a malicious Python package release.
Microsoft said the malware ran on every Python startup, and stolen AWS keys were checked against Amazon AI models.

An unrevoked Agent Platform key from May let an attacker publish LiteLLM 1.107.0 to PyPI on October 21; PyPI later quarantined it.

October 10 and 12 workflows posted CI secrets to webhook.site; a key committed May 27 was never revoked.

Starting Python with the package installed can run PRIVCOLLECT without importing LiteLLM; removing the package does not recover credentials.

The digest says many incidents were found earlier and disclosed together, while exploitation scale is disputed.

The poisoned build was online about three hours, downloaded over 49,000 times, and the latest clean release is 1.106.2.

Malicious LiteLLM 1.107.0 wheels and images were live for hours on October 21; roll back to 1.106.2 and rotate secrets.

The same live feed also covers BIND GSS-TSIG memory corruption, Node.js security releases, bank AI-agent logins and a Railway environment-variable incident.

The build stayed up for under two hours on PyPI; anyone who installed it is told to rotate credentials, not only upgrade.

Malicious version 1.107.0 stayed on PyPI for about two hours on October 21 before removal.

Unpinned installs for a few hours on October 21 pulled a credential stealer and an hourly remote-code backdoor.

The supplied page text does not describe the malicious packages, payloads, or who was affected.

Fixed PHP builds are 8.5.12, 8.4.27, 8.3.36, and 8.2.35; LiteLLM 1.107.0 stole secrets, so pin 1.106.2 and rotate them.

Malicious Python startup hooks can collect cloud and AI credentials even when applications never import LiteLLM.

NSA told PHP users to update or go offline; LiteLLM malicious packages stole credentials and included a RAT.
PyPI and Docker removed the trojanized release within hours; the latest safe version named is v1.106.2.

PyPI quarantined the release and Docker images were removed; users should pin 1.106.2 and rotate exposed credentials.
Today 1.5K readers · 2.4K views · 754 reads · all time 189K views