
Unpinned MCP server launches can expose API keys, Corelight finds
Of 35 servers reviewed, 23 recommended installs pulled fresh registry dependencies; pinning the main package did not lock the rest.
44 stories, newest first · one card per story

Of 35 servers reviewed, 23 recommended installs pulled fresh registry dependencies; pinning the main package did not lock the rest.

The security tab shows per-file attestations and flags incomplete, inconsistent, changed, or lost provenance before install.

Accounts henrywoo and kitao added the workflow on October 8; it exfiltrates secrets over HTTP and scans Git history.
Poisoned release 1.107.0 carried an infostealer and remote access trojan and drew about 49,000 downloads before PyPI quarantined it.
Microsoft said the malware ran on every Python startup, and stolen AWS keys were checked against Amazon AI models.
An oss-security reply says a report also covers the issue and that PyPI brotli packages were added to a vulnerable-package list.

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 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 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.

Malicious Python startup hooks can collect cloud and AI credentials even when applications never import LiteLLM.
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.

All seven wheels and several Docker tags were tainted; PyPI removed the release, and Wiz calls 1.106.2 the latest safe build.

All seven wheels run the implants in every Python process; PyPI removed the release, and 1.106.2 plus two release candidates are clean.

PyPI quarantined the upload within about two hours; matching Docker tags included latest, main-latest and main-stable.

PyPI and official Docker tags carried the release for about two hours; the RAT dead-drop never delivered a live second stage.
A source check blocked 87.7 to 99.9 percent of 47,066 malicious packages, depending on how strictly the source was vetted.

OpenSourceMalware's count through October 9 is validated public repos, not proof that every one leaked secrets.
Today 1.5K readers · 2.4K views · 754 reads · all time 189K views