[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7xftYtNcTIGDCVrT91HiJJO1_QIo51C5qZqXYA9ma6A":3},{"article":4,"iocs":52,"watch_terms":53,"solutions":54,"lesson":136},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":29,"category":30,"article_tags":34},"8d0509e4-17ce-4db9-9b98-657e26ee081a","CrowdSec Confirms Source Code Stolen in Supply Chain Attack","crowdsec-confirms-source-code-stolen-in-supply-chain-attack-041aae","The cybersecurity firm believes the data breach was the result of the May 2026 TanStack supply chain attack. The post CrowdSec Confirms Source Code Stolen in Supply Chain Attack appeared first on SecurityWeek.","French cybersecurity firm CrowdSec has confirmed that its GitHub repositories were compromised, resulting in the theft of source code from approximately 300 repositories, including 170 private ones. The company believes this breach was a consequence of the May 2026 TanStack supply chain attack, where malware likely exploited an API key to access CrowdSec's private codebase. CrowdSec stated that no customer data was leaked and the stolen code is unlikely to pose an immediate threat outside of its own environment.","CrowdSec confirms source code stolen in supply chain attack via TanStack compromise.","https:\u002F\u002Fwww.securityweek.com\u002Fcrowdsec-confirms-source-code-stolen-in-supply-chain-attack\u002F","https:\u002F\u002Fwww.securityweek.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FCode-3rd-Party-Risk.jpg","2026-09-21T10:55:46+00:00","2026-09-21T12:00:44.120553+00:00",8,[17,20,23,26],{"name":18,"type":19},"CrowdSec","vendor",{"name":21,"type":22},"TanStack","product",{"name":24,"type":25},"TeamPCP","threat_actor",{"name":27,"type":28},"GitHub","technology","26b0b636-0e31-4db1-bffb-61bdf9f20a58",{"id":29,"icon":31,"name":32,"slug":33},null,"Supply Chain","supply-chain",[35,37,42,47],{"category":36},{"id":29,"icon":31,"name":32,"slug":33},{"category":38},{"id":39,"icon":31,"name":40,"slug":41},"2e06f76c-d5b9-4f54-9eef-4d3447b10730","Breaches","breaches",{"category":43},{"id":44,"icon":31,"name":45,"slug":46},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",{"category":48},{"id":49,"icon":31,"name":50,"slug":51},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[18,21],{"controls":55,"vendors":135},[56,84,113],{"slug":57,"name":58,"problem":59,"products":60},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",[61,68,76],{"vendor_slug":62,"vendor_name":27,"vendor_logo":63,"product_slug":64,"product_name":65,"url":66,"description":67},"github","\u002Fvendor-logos\u002Fgithub.png","advanced-security","GitHub Advanced Security","https:\u002F\u002Fgithub.com\u002Fsecurity\u002Fadvanced-security","Dependency review, code scanning and secret scanning with push protection.",{"vendor_slug":69,"vendor_name":70,"vendor_logo":71,"product_slug":72,"product_name":73,"url":74,"description":75},"gitguardian","GitGuardian","\u002Fvendor-logos\u002Fgitguardian.png","gitguardian-platform","GitGuardian Secrets Detection","https:\u002F\u002Fwww.gitguardian.com\u002F","Finds and helps remediate secrets leaked in repositories, CI pipelines and chat tools.",{"vendor_slug":77,"vendor_name":78,"vendor_logo":79,"product_slug":80,"product_name":81,"url":82,"description":83},"hashicorp","HashiCorp","\u002Fvendor-logos\u002Fhashicorp.png","vault","HashiCorp Vault","https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fproducts\u002Fvault","Secrets management with short-lived credentials and encryption as a service.",{"slug":85,"name":86,"problem":87,"products":88},"third-party-risk-management","Third-party risk management (TPRM)","You know which suppliers could hurt you, and you hear quickly when one of them is breached.",[89,97,105],{"vendor_slug":90,"vendor_name":91,"vendor_logo":92,"product_slug":93,"product_name":94,"url":95,"description":96},"bitsight","Bitsight","\u002Fvendor-logos\u002Fbitsight.png","bitsight-tprm","Bitsight Third-Party Risk Management","https:\u002F\u002Fwww.bitsight.com\u002Fproducts\u002Fthird-party-risk-management","Supplier assessments and continuous monitoring based on security ratings.",{"vendor_slug":98,"vendor_name":99,"vendor_logo":100,"product_slug":101,"product_name":102,"url":103,"description":104},"upguard","UpGuard","\u002Fvendor-logos\u002Fupguard.png","upguard-vendor-risk","UpGuard Vendor Risk","https:\u002F\u002Fwww.upguard.com\u002Fproduct\u002Fvendor-risk","Supplier security questionnaires, ratings and continuous monitoring.",{"vendor_slug":106,"vendor_name":107,"vendor_logo":108,"product_slug":109,"product_name":110,"url":111,"description":112},"securityscorecard","SecurityScorecard","\u002Fvendor-logos\u002Fsecurityscorecard.png","security-ratings","SecurityScorecard Ratings","https:\u002F\u002Fsecurityscorecard.com\u002Fsolutions\u002Fuse-cases\u002Fsecurity-ratings\u002F","Outside-in security ratings and monitoring of suppliers.",{"slug":114,"name":115,"problem":116,"products":117},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship.",[118,126,127],{"vendor_slug":119,"vendor_name":120,"vendor_logo":121,"product_slug":122,"product_name":123,"url":124,"description":125},"sonatype","Sonatype","\u002Fvendor-logos\u002Fsonatype.png","sonatype-firewall","Sonatype Firewall","https:\u002F\u002Fwww.sonatype.com\u002Fproducts\u002Fsonatype-firewall","Blocks malicious and policy-violating open-source components at download.",{"vendor_slug":62,"vendor_name":27,"vendor_logo":63,"product_slug":64,"product_name":65,"url":66,"description":67},{"vendor_slug":128,"vendor_name":129,"vendor_logo":130,"product_slug":131,"product_name":132,"url":133,"description":134},"jfrog","JFrog","\u002Fvendor-logos\u002Fjfrog.png","jfrog-xray","JFrog Xray","https:\u002F\u002Fjfrog.com\u002Fxray\u002F","Software composition analysis and SBOM generation for artifacts.",[],{"slug":137,"title":138,"body":139,"framework_refs":140,"framework_notes":151},"crowdsec-source-code-stolen-via-third-party-supply-chain-attack","CrowdSec Source Code Stolen via Third-Party Supply Chain Attack","CrowdSec's GitHub repositories were compromised as a downstream consequence of the TanStack supply chain attack, where malware likely harvested an API key that granted access to approximately 300 repositories, including 170 private ones. This incident illustrates how a single compromised third-party dependency can cascade into a serious breach for organizations that trust it — even security-focused companies are not immune. The exposure of proprietary source code, while not immediately weaponizable externally, can enable adversaries to identify hidden vulnerabilities, hardcoded secrets, or internal architecture details for future attacks. This underscores the critical need to treat third-party integrations as potential attack vectors and to apply the principle of least privilege to all API credentials and tokens.",[141,142,143,144,145,146,147,148,149,150],"CIS Control 2: Inventory and Control of Software Assets","CIS Control 6: Access Control Management","CIS Control 12: Network Infrastructure Management","NIST SP 800-161: Cybersecurity Supply Chain Risk Management","NIST AC-2: Account Management","NIST AC-6: Least Privilege","NIST SR-6: Supplier Assessments and Reviews","NIST DE.CM-3: Personnel Activity Monitoring","ISO\u002FIEC 27001 A.15: Supplier Relationships","SLSA Framework: Supply-chain Levels for Software Artifacts",{}]