300+
GitHub Repos Stolen
3M+
Salesforce Records
Apr 3
Extortion Deadline
6+
Gov Agencies in Data
The Full Chain: From Trivy to Cisco
This story started on March 19 when TeamPCP compromised Aqua Security's Trivy vulnerability scanner. We covered that attack in detail on March 25. The key insight was that Trivy runs in CI/CD pipelines with broad access to secrets, credentials, and environment variables. When TeamPCP injected their credential stealer into Trivy's GitHub Actions, every organization that ran Trivy during the compromise window had their CI/CD secrets harvested and exfiltrated.
Cisco was one of those organizations. Cisco's internal development environment used Trivy as part of its build process. When the compromised Trivy action executed in Cisco's CI/CD pipeline, it harvested credentials from the runner environment, including AWS access keys and tokens with access to Cisco's internal infrastructure.
Using those stolen credentials, the attackers bypassed Cisco's authentication controls and gained access to its internal build environments. Once inside, they compromised dozens of devices including lab workstations and developer systems. From those systems, they cloned over 300 private GitHub repositories. BleepingComputer reported that the stolen repositories include source code for Cisco's AI Assistant, AI Defense, and other unreleased AI products. Some repositories allegedly belong to corporate customers, including banks, business process outsourcing companies, and US government agencies.
The AWS keys were used to perform unauthorized operations inside Cisco's cloud accounts. ShinyHunters posted screenshots showing the AWS EC2 Volumes console with dozens of virtual storage drives and an S3 bucket listing. Some drive creation dates fall on March 16-17, 2026, indicating the access may have begun even before the Trivy compromise was publicly detected.
The Salesforce Exposure
ShinyHunters claims the breach extends beyond the development environment. They report over 3 million Salesforce CRM records containing personally identifiable information were exfiltrated. The data reportedly came through three separate access paths: a voice phishing (vishing) attack attributed to UNC6040 (which Cisco previously disclosed last summer), exploitation of Salesforce Aura (Experience Cloud) guest user access controls, and the AWS account compromise.
The Salesforce angle is the most consequential for downstream impact. Resecurity's threat intelligence analysis reports that the stolen Salesforce data includes records tied to personnel from the FBI, DHS, DISA, IRS, NASA, the Australian Ministry of Defense, and multiple Indian government agencies. These records are likely associated with procurement, configuration, and support interactions for Cisco networking products used by those agencies.
This data is exceptionally valuable for adversaries planning targeted phishing, social engineering, or supply chain attacks against government personnel. Names, email addresses, phone numbers, and account metadata for government IT personnel who manage Cisco infrastructure provide a ready-made target list for follow-on operations. The exposure is not limited to Cisco. It extends to every government agency whose personnel data sits in Cisco's Salesforce instance.
The Adversary Perspective
The convergence of ShinyHunters and TeamPCP represents a new operational model in cybercrime. TeamPCP provides the initial access through supply chain compromise. ShinyHunters provides the extortion and monetization capability. Together, they cover the full attack lifecycle from supply chain exploitation through data theft to ransom negotiation.
The Trivy-to-Cisco chain validates the cascading credential theft model. TeamPCP did not target Cisco directly. They targeted a security tool that Cisco used. The credential harvester in the compromised Trivy action collected everything accessible from CI/CD runner memory. One of those credentials happened to unlock Cisco's internal infrastructure. This is not targeted exploitation. It is credential harvesting at scale with downstream exploitation of whatever the credentials unlock. The attacker does not need to know who uses Trivy. They just need to steal everything and sort through the results.
The multi-vector approach makes verification and response difficult. ShinyHunters claims three separate breach vectors: vishing, Salesforce Aura, and AWS. One of these (the vishing attack) was already disclosed by Cisco last summer. The Salesforce Aura exploitation may represent a broader campaign: ShinyHunters reportedly exploited misconfigured Salesforce Experience Cloud guest user access at 300 to 400 organizations using an open-source tool called AuraInspector. The AWS compromise is linked to the Trivy supply chain attack. Defenders are not responding to one incident. They are responding to three overlapping incidents with different timelines, different entry points, and different data exposure profiles.
The source code theft creates long-term strategic risk. Stolen source code for unreleased AI products gives competitors and nation-state actors insight into Cisco's product roadmap, architectural decisions, and potential vulnerabilities before the products ship. If the AI Defense source code contains the security logic for Cisco's AI-era security products, adversaries can study it for bypass techniques before the product reaches market. This is not a data breach that can be resolved with credit monitoring. It is an intellectual property loss with multi-year competitive implications.
Figure 01
- MAR 19
TeamPCP Compromises Trivy
Malicious GitHub Action plugin injected into Trivy's CI/CD pipeline. Credential stealer harvests secrets from every organization that runs Trivy. Cisco's dev environment pulls the compromised Trivy action. - MAR 16-19 // CRITICAL
Cisco Credentials Stolen
Trivy credential stealer harvests AWS keys and CI/CD tokens from Cisco's build runners. Some AWS volume creation dates suggest access as early as March 16. Credentials exfiltrated to TeamPCP infrastructure. - MAR 19-31 // CRITICAL
Cisco Development Environment Breached
Stolen credentials used to access Cisco's internal build systems. Dozens of lab workstations and developer machines compromised. 300+ private GitHub repos cloned, including AI Assistant, AI Defense, and unreleased AI products. AWS keys used for unauthorized cloud operations. - PARALLEL
Salesforce Aura Exploitation
ShinyHunters exploits misconfigured Salesforce Experience Cloud guest user access controls using AuraInspector tool. 3M+ CRM records exfiltrated including PII for Cisco customers, employees, and government agency personnel (FBI, DHS, DISA, IRS, NASA, Australian MOD, Indian govt). - MAR 31
ShinyHunters Posts Extortion
ShinyHunters claims responsibility on dark web. "FINAL WARNING" notice with April 3 deadline. Screenshots of AWS EC2 volumes and S3 bucket lists. Threatens "several annoying (digital) problems" if demands not met. - ONGOING // CRITICAL
Cisco Incident Response
Cisco's CSIRT, Unified Intelligence Center, and EOC responding. Compromised systems isolated. Affected machines wiped and reinstalled. Mass employee credential reset enforced. No public statement on full scope. April 3 deadline approaching.
Incident Summary
- Victim: Cisco Systems
- Threat Actors: ShinyHunters (extortion), TeamPCP (supply chain access)
- Initial Access: Trivy supply chain compromise (CVE-2026-33634)
- Secondary Vectors: Vishing (UNC6040, disclosed 2025), Salesforce Aura exploitation
- Data Stolen: 300+ private GitHub repos (AI Assistant, AI Defense, unreleased products)
- Data Stolen: 3M+ Salesforce CRM records with PII
- Data Stolen: AWS EC2 volumes, S3 bucket contents, cloud configurations
- Gov Data Exposure: FBI, DHS, DISA, IRS, NASA, Australian MOD, Indian govt agencies
- Customer Data: Repos allegedly from banks, BPOs, US government agencies
- Extortion Deadline: April 3, 2026
- Cisco Response: System isolation, device wipe/reinstall, mass credential reset
- Cisco Public Statement: Not issued on full scope as of publication
- Prior Related: IntelBroker DevHub incident (Oct 2024, 4.5TB exposed via misconfiguration)
Defensive Takeaways
- 1
If You Used Trivy Between March 16-24, You May Be a Downstream Victim
Cisco is the highest-profile confirmed victim, but they are not the only organization that ran Trivy during the compromise window. If your CI/CD pipelines used Trivy between March 16 and March 24, your credentials were potentially harvested. Audit your CI/CD runner logs. Check for the TeamPCP IOCs we published on March 25. Rotate all secrets that were accessible from those runners. The fact that your organization has not been publicly extorted does not mean your credentials were not stolen. It may mean the attackers have not yet processed your credentials in their queue.
- 2
Audit Your Salesforce Experience Cloud (Aura) Guest User Configuration
ShinyHunters reportedly exploited misconfigured Salesforce Experience Cloud guest user access controls at 300 to 400 organizations. The tool they used, AuraInspector, is open source and scans for these misconfigurations automatically. If your organization runs Salesforce Experience Cloud (formerly Communities), audit guest user permissions immediately. Ensure guest users cannot access object records, profile data, or PII through the Aura API. Review OAuth-connected apps and revoke unrecognized tokens. Monitor for unauthorized Salesforce Data Loader activity. This is not a Cisco-specific issue. If you run Salesforce Aura, you may be in ShinyHunters' broader campaign.
- 3
Treat Development Environments as High-Value Targets
The Cisco breach originated in the development environment, not in production. Dev environments contain source code, build secrets, cloud credentials, customer data, and access to production deployment pipelines. They are often less secured than production because the cultural assumption is that "dev" means "lower risk." This breach demonstrates the opposite. The source code for Cisco's unreleased AI products, the AWS keys to their cloud infrastructure, and the access paths to 300+ customer repos were all accessible from the development environment. Harden your dev environments with the same rigor you apply to production. Segment them. Monitor them. Restrict what credentials they can access.
- 4
Prepare for Downstream Exposure If You Are a Cisco Customer
If your organization is a Cisco customer, particularly if you are a government agency, financial institution, or large enterprise with procurement, support, or configuration data in Cisco's Salesforce instance, your personnel data may be in the stolen records. Brief your security team and your employees who interact with Cisco. Expect targeted phishing using legitimate Cisco contact details, support ticket references, and procurement information. The stolen data gives attackers the context to craft highly convincing social engineering campaigns against your staff, using information that appears to come from a trusted vendor relationship.
- 5
This Is the Supply Chain Story We Have Been Warning About All Month
On March 25, we published our analysis of TeamPCP's cascading supply chain attack and wrote that each compromised environment yields credentials that unlock the next target. Cisco is that next target. The chain ran from Trivy (security scanner) to Checkmarx (security scanner) to LiteLLM (AI proxy) to Telnyx (communications) to Cisco (networking giant). Each link was unlocked by credentials stolen from the previous link. If your organization consumes open source software in CI/CD pipelines, the question is not whether you are in a supply chain. The question is whether you have visibility into every dependency that runs in your build environment, what credentials those dependencies can access, and whether you would detect a compromise before the attacker uses your stolen credentials against your own infrastructure or passes them to a partner group for extortion.