The Point: Developer workstations are a critical attack vector. Attackers are increasingly focusing on credential harvesting from developer environments. Security teams must align their protection strategies to this new reality of the software supply chain.
Attackers targeting the software supply chain are increasingly focused on stealing access credentials from developer environments. Within a 48-hour window, three separate campaigns targeted npm, PyPI, and Docker Hub, demanding API keys, cloud credentials, SSH keys, and tokens. This development forces security teams to fundamentally reconsider their protection strategy.
Security teams need to reassess their view of the software supply chain. Traditionally, the focus centered on shared systems such as source code repositories, CI/CD platforms, artifact registries, package managers, and cloud environments. While these areas remain important, the picture is incomplete.
Modern software development begins before code arrives in Git – on the developer workstation. This is where developers write code, install dependencies, test credentials, use AI assistants, create containers, and initiate trusted actions. Developer workstations are thus a real part of the supply chain.
Recent attack campaigns such as TeamPCP and Shai-Hulud demonstrate a clear pattern: regardless of the method – poisoned packages, compromised images, manipulated workflows, or vulnerable developer tools – the real objective is always access. In the TeamPCP campaign, attackers used compromised packages and developer tools to harvest tokens, cloud credentials, SSH keys, and environment variables. Shai-Hulud took this approach further, transforming infected developer environments into collection points for thousands of secrets.
The critical point: developer workstations concentrate valuable context. They locally contain repositories, .env files, shell history, and package manager configurations. When attackers gain access to these credentials and contexts, they can alter, publish, build, and deploy trusted software systems – or impersonate them. Modern supply chain attacks often persist for hours, while automation tools can introduce malware updates in minutes.