[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5-KkYXHigtNn4KGNVq3OV6T5t85N3BOlKPl_AXiul8k":3},{"article":4,"iocs":52,"watch_terms":58,"solutions":59,"lesson":142},{"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},"c8caef8e-dba3-4920-9d53-737f99f10ee6","LiteLLM supply chain attack started with an exposed master key","litellm-supply-chain-attack-started-with-an-exposed-master-key-3bd252","A 'strong illustration of the risks associated with failing to rotate a potentially exposed key'","LiteLLM experienced a supply chain attack where a master key was accidentally committed to a public GitHub repository. This key allowed an attacker to gain owner-level access to LiteLLM's GitHub repositories, enabling them to inject malicious code into the LiteLLM package distributed via PyPI. The compromised package, version 1.107.0, contained an infostealer and a remote access trojan, leading to the potential exfiltration of sensitive credentials and API keys.","LiteLLM supply chain attack began with an exposed master key on GitHub.","https:\u002F\u002Fwww.theregister.com\u002Fsecurity\u002F2026\u002F10\u002F26\u002Flitellm-supply-chain-attack-started-with-an-exposed-master-key\u002F5305544","https:\u002F\u002Fimage.theregister.com\u002F?imageId=5263597&width=800","2026-10-26T20:30:53+00:00","2026-10-26T21:00:06.518324+00:00",9,[17,20,23,25,27],{"name":18,"type":19},"LiteLLM","product",{"name":21,"type":22},"AI gateway","technology",{"name":24,"type":22},"LLM",{"name":26,"type":22},"open source",{"name":28,"type":22},"GitHub CLI OAuth token","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},"839da5c1-3c34-47e2-9499-f7201640e3ac","AI Security","ai-security",{"category":43},{"id":44,"icon":31,"name":45,"slug":46},"89f78b1c-3503-45a1-9fc7-e23d2ce1c6d5","Malware","malware",{"category":48},{"id":49,"icon":31,"name":50,"slug":51},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",[53,56],{"type":46,"value":54,"context":55},"infostealer","Malicious payload within compromised LiteLLM package",{"type":46,"value":57,"context":55},"remote access trojan",[18],{"controls":60,"vendors":141},[61,90,119],{"slug":62,"name":63,"problem":64,"products":65},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",[66,74,82],{"vendor_slug":67,"vendor_name":68,"vendor_logo":69,"product_slug":70,"product_name":71,"url":72,"description":73},"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.",{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":78,"product_name":79,"url":80,"description":81},"github","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":83,"vendor_name":84,"vendor_logo":85,"product_slug":86,"product_name":87,"url":88,"description":89},"palo-alto-networks","Palo Alto Networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","idira-secrets-management","Idira Secrets Management","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fidira\u002Fmachine\u002Fsecrets-management","Secrets management for applications, scripts and pipelines, from the former CyberArk portfolio.",{"slug":91,"name":92,"problem":93,"products":94},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[95,103,111],{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"vendor_slug":104,"vendor_name":105,"vendor_logo":106,"product_slug":107,"product_name":108,"url":109,"description":110},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"vendor_slug":112,"vendor_name":113,"vendor_logo":114,"product_slug":115,"product_name":116,"url":117,"description":118},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"slug":120,"name":121,"problem":122,"products":123},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship.",[124,132,133],{"vendor_slug":125,"vendor_name":126,"vendor_logo":127,"product_slug":128,"product_name":129,"url":130,"description":131},"jfrog","JFrog","\u002Fvendor-logos\u002Fjfrog.png","jfrog-xray","JFrog Xray","https:\u002F\u002Fjfrog.com\u002Fxray\u002F","Software composition analysis and SBOM generation for artifacts.",{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":78,"product_name":79,"url":80,"description":81},{"vendor_slug":134,"vendor_name":135,"vendor_logo":136,"product_slug":137,"product_name":138,"url":139,"description":140},"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.",[],{"slug":143,"title":144,"body":145,"framework_refs":146,"framework_notes":154},"litellm-master-key-exposure-enables-supply-chain-attack-via-pypi","LiteLLM Master Key Exposure Enables Supply Chain Attack via PyPI","A developer accidentally committed a master key to a public GitHub repository, granting an attacker owner-level access to LiteLLM's entire GitHub organization. With that access, the attacker injected an infostealer and remote access trojan into version 1.107.0 of the LiteLLM PyPI package, potentially compromising credentials and API keys of every downstream user who installed it. This incident illustrates how a single secret exposure can cascade into a full supply chain compromise affecting thousands of consumers. Secrets in source code are a well-documented, preventable risk that automated scanning tools can catch before they ever reach a public repository.",[147,148,149,150,151,152,153],"CIS Control 4: Secure Configuration of Enterprise Assets and Software","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","NIST SP 800-53 SI-2: Flaw Remediation","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","OWASP A06:2021 Vulnerable and Outdated Components","MITRE ATT&CK T1566: Phishing","NIS2 Article 21(2)(b)",{"NIS2 Article 21(2)(b)":155,"MITRE ATT&CK T1566: Phishing":156,"NIST SP 800-53 SI-2: Flaw Remediation":157,"OWASP A06:2021 Vulnerable and Outdated Components":158,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":159,"CIS Control 4: Secure Configuration of Enterprise Assets and Software":160,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":161},"NIS2 requires entities to implement incident handling and supply chain security measures; LiteLLM's failure to prevent secret exposure and detect the malicious package injection before distribution represents a gap in both requirements.","The attacker's initial foothold via an exposed credential is analogous to credential theft techniques catalogued in ATT&CK; specifically, the subsequent repository takeover mirrors T1195 (Supply Chain Compromise), highlighting the need for integrity controls across the software delivery pipeline.","Timely detection and removal of the exposed secret, combined with rapid revocation and re-issuance, aligns with SI-2's requirement to identify and correct software and configuration flaws promptly.","Downstream consumers installing the trojanized LiteLLM package were unknowingly using a compromised component, which is precisely the risk OWASP A06 addresses by requiring verification of component integrity and provenance.","This control requires organizations to identify and remediate technical vulnerabilities in a timely manner; automated secret-scanning in CI\u002FCD would have surfaced the committed key as a vulnerability before it was exploited.","Proper secret management practices—keeping credentials out of source code and using environment variables or vaults—fall under secure configuration and would have prevented the master key from being exposed in the public repository.","Applying least-privilege to the master key so it did not carry owner-level GitHub organization access would have dramatically limited the blast radius when the credential was exposed."]