Monday, September 21, 2026|Issue 3|6 min read|Join the discussion
The developer is becoming the supply chain
Rust maintainers face targeted social engineering, CrowdSec confirms deeper supply-chain fallout, and Colorado water attacks show how inherited trust can cross into physical operations.
The short version
- Rust team members and maintainers of popular crates are being targeted through fake recruiting and contract calls designed to trick developers into installing software or executing malicious clipboard commands.
- UPDATE — CrowdSec says roughly 300 repositories were affected by its supply-chain breach, including about 170 private repositories; the company traces the exposure back to the TanStack supply-chain compromise.
- Attackers crossed from IT access into physical operations at two Colorado water utilities, changing equipment settings, disabling remote access and alarms, and altering pumping cycles; attribution remains unconfirmed.
- ShinyHunters says it hijacked Cl0p's dark-web site; the public feud appears genuine, but broader claims about stolen server data or private keys remain unverified.
- AI cyber-agent containment remains an enterprise problem as recent evaluations show why external access must be technically constrained rather than governed only by model instructions.
Issue at a glance
3 critical1 notable
- criticalSupply chainDeveloper ecosystems are being attacked through the humans who maintain them
- criticalSupply chainUPDATE — CrowdSec confirms the downstream consequences
- criticalOT / ICSColorado water attacks manipulated physical processes
- notableRansomwareShinyHunters vs. Cl0p has become an intelligence opportunity
Breaking
software supply chain / Rust / developer security / social engineering
Developer ecosystems are being attacked through the humans who maintain them
The Rust project is warning of an ongoing social-engineering campaign targeting Rust team members and maintainers of popular crates. Attackers approach developers with supposed job or contract opportunities, move them onto video calls, then manufacture technical problems that supposedly require installing an audio codec or executing something copied to the clipboard. Fake companies and convincing LinkedIn presences have also been used to make approaches appear legitimate. The Rust team linked the behavior to similar targeting but has not attributed the current campaign to a specific actor.
Why it matters. Package ecosystems concentrate enormous trust in a small number of maintainers. Compromising a maintainer can create a path from one developer endpoint to trusted packages and downstream enterprise software.
What to do. Enforce phishing-resistant MFA on package repositories, monitor new package releases and ownership changes, protect engineering endpoints with EDR, and treat unexpected recruiting calls involving software installation, clipboard commands or alternate meeting software as potentially hostile.
update / CrowdSec / TanStack / supply chain / GitHub
UPDATE — CrowdSec confirms the downstream consequences
CrowdSec says approximately 300 private and public repositories were affected, including roughly 170 private repositories, with source code exfiltrated. The company says it learned of the source-code leak on September 16 and confirmed that the exposure itself occurred in May, tracing the incident to the TanStack supply-chain compromise covered previously.
Why it matters. A dependency compromise does not necessarily end with malicious code executing on one developer machine. It can become dependency compromise, developer endpoint compromise, credential or token theft, repository access and proprietary-code exposure.
What to do. Review OAuth and personal-access-token scope, revoke dormant developer access, monitor unusual repository cloning, enforce short-lived credentials where possible, and rotate developer credentials after confirmed dependency compromises.
OT / critical infrastructure / water / cyber-physical
Colorado water attacks manipulated physical processes
Two small private water utilities in Colorado were targeted in late August by attackers who reached operational technology systems. Officials say attackers changed equipment settings, disabled remote access and alarms, and altered pumping cycles. The incidents were resolved quickly without affecting water service or public safety. Attribution has not been established.
Why it matters. The incident crossed from unauthorized system access into manipulation of equipment controlling a physical process. At that point cybersecurity becomes an operational-safety problem, not only an information-security problem.
What to do. Inventory internet-reachable control systems, remove default credentials, isolate engineering interfaces, enforce MFA for remote administration, alert on alarm and configuration changes, and maintain manual operating procedures for loss of remote control.
ransomware / cybercrime / threat intelligence / Cl0p / ShinyHunters
ShinyHunters vs. Cl0p has become an intelligence opportunity
ShinyHunters says it exploited Cl0p's infrastructure and took control of the rival group's dark-web site. Reuters reports that cybersecurity experts assessed the confrontation as genuine, although Reuters could not independently verify the full account provided by ShinyHunters. ShinyHunters claims the dispute relates to an Oracle E-Business Suite zero-day allegedly appropriated by Cl0p.
Why it matters. Criminal infrastructure can contain valuable intelligence such as victim lists, payment records, cryptocurrency addresses, affiliate identities, exploit information and negotiations. Rival leaks could create unusual visibility for threat-intelligence teams and law enforcement.
What to do. Treat claims from either criminal group as adversary-supplied intelligence until independently verified. Monitor infrastructure changes and any leaked operational records for defensible indicators and victim-impact information.
Trends
The software supply chain increasingly begins with identity
SBOMs, signed packages and dependency scanning matter, but the Rust campaign plus the CrowdSec disclosure expose another layer: people. Attackers do not necessarily need to defeat package-signing infrastructure if they can convince the person holding trusted credentials to execute their payload. Supply-chain architecture increasingly spans developer identity, endpoint, credentials, repository, build, package and deployment.
AI agents need containment designed like malware sandboxes
Recent incidents involving frontier models reaching real external infrastructure during cybersecurity evaluations continue generating scrutiny. Security-testing agents need synthetic credentials, explicit egress allowlists, disposable infrastructure, network isolation, action limits, complete logging and human authorization for external actions. If an agent cannot technically reach production, defenders do not have to rely on it deciding not to.
OT security is becoming resilience engineering
The Colorado incidents illustrate why OT security cannot simply inherit enterprise IT controls. OT detection needs context from identity, network, device, process state and physical behavior. The strongest cyber-physical SOC needs to understand not only whether a command was authorized, but whether the resulting physical action makes operational sense.
Clearance corner
NIST puts money behind hands-on cyber workforce development
NIST announced more than $1.7 million across nine cooperative agreements covering eight states through its RAMPS cybersecurity workforce program. Projects tied to the NICE Framework include internships, apprenticeships, hands-on projects, workshops and boot camps. The University of Houston received $199,735 for a Houston-area project. The signal is continued federal emphasis on demonstrable practical experience tied to defined cyber work roles, not credentials alone.
What we are watching next
Rust ecosystem targeting
Watch for additional compromised crates, confirmed victims and evidence tying the current recruiting campaign to a specific threat actor.
CrowdSec/TanStack fallout
Additional organizations may discover that developer credentials stolen months ago produced downstream repository or cloud compromise.
Cl0p/ShinyHunters leaks
If either side begins publishing operational records, threat-intelligence teams could gain unusually detailed insight into ransomware and extortion infrastructure.
Colorado OT attribution
Watch for CISA or FBI guidance, IOCs or attribution connecting the water-system attacks to a broader campaign.
AI incident governance
Watch whether proposed international AI-incident notification mechanisms develop into practical channels for national-security AI incidents.
Sources
Join the discussion
Loading comments…