<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Teampcp on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/teampcp/</link><description>Recent content in Teampcp on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Apr 2026 11:30:31 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/teampcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Bitwarden CLI Backdoored on npm for 93 Minutes</title><link>https://hackingpassion.com/bitwarden-cli-supply-chain-attack/</link><pubDate>Fri, 24 Apr 2026 11:30:31 +0200</pubDate><guid>https://hackingpassion.com/bitwarden-cli-supply-chain-attack/</guid><description>&lt;p>Bitwarden&amp;rsquo;s CLI was backdoored and pushed to npm on April 22, 2026. It was live for &lt;strong>93 minutes&lt;/strong>. Every developer who installed it during that window has to treat their &lt;strong>entire machine as compromised&lt;/strong>. GitHub tokens, SSH keys, AWS credentials, cloud secrets. All of it.&lt;/p>
&lt;p>If you followed the Shai-Hulud story back in November 2025, this will sound familiar. That attack spread through npm and hit packages from Zapier, Postman, PostHog, and hundreds of others. &lt;strong>132 million monthly downloads affected.&lt;/strong> Stolen credentials dumped into public GitHub repositories for anyone to find. This new attack names itself &lt;strong>Shai-Hulud: The Third Coming&lt;/strong>, after the giant sandworms from Frank Herbert&amp;rsquo;s Dune. The irony is that this third wave specifically targets AI tools.&lt;/p></description></item><item><title>How TeamPCP Poisoned Six Python Packages and Breached Over 1000 Organizations in Five Weeks</title><link>https://hackingpassion.com/pypi-supply-chain-attack-xinference-teampcp/</link><pubDate>Thu, 23 Apr 2026 11:10:52 +0200</pubDate><guid>https://hackingpassion.com/pypi-supply-chain-attack-xinference-teampcp/</guid><description>&lt;p>A group of attackers has been quietly poisoning Python packages for five weeks straight. They have exfiltrated data from over &lt;strong>500,000 infected machines&lt;/strong>, hit more than &lt;strong>1,000 organizations&lt;/strong>, and confirmed victims include &lt;strong>Aqua Security&lt;/strong>, &lt;strong>Checkmarx&lt;/strong>, and government infrastructure including the &lt;strong>European Commission&amp;rsquo;s AWS environment&lt;/strong>. Yesterday they struck again. This time the target was &lt;strong>Xinference&lt;/strong>, an open-source framework used by developers to run AI models locally. Versions &lt;strong>2.6.0&lt;/strong>, &lt;strong>2.6.1&lt;/strong>, and &lt;strong>2.6.2&lt;/strong> were compromised and have since been pulled from PyPI. If you installed or updated Xinference in the last 24 hours without pinning your version, you need to act now.&lt;/p></description></item></channel></rss>