[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5bhTySfLXU_Brb7RqQNvuk4M7Gl877MTW4s-lonZqms":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":44},"e3e4af00-806c-4ceb-ac03-288d138ee0b3","malicious-pypi-packages-stole-cloud-credentials-in-minutes","a021abf8-c92c-4e86-a8b6-2379eced370a","Malicious PyPI Packages Stole Cloud Credentials in Minutes","Two trojanized versions of the agent-framework package were uploaded to PyPI within 33 minutes of each other, embedding a credential stealer that executed automatically on Python startup — targeting Azure, Azure DevOps, and GitHub Actions secrets. This is a classic supply chain attack: developers who updated their dependency during that window would have silently compromised their cloud credentials without any obvious warning. The speed of the attack (two versions, rapid deployment) suggests a deliberate strategy to maximize exposure before detection. This incident highlights how much implicit trust developers place in public package registries and how quickly a poisoned dependency can propagate through CI\u002FCD pipelines. Organizations without dependency integrity checks or behavioral monitoring had no automated way to detect the malicious code before damage was done.","**Immediate actions:**\n- Pin all third-party dependencies to known-good, explicitly verified version hashes in your lockfiles (e.g., `pip` with `--require-hashes`).\n- Audit your current Python environments for any installations of agent-framework versions 1.26.1 or 1.26.2 and rotate all Azure, Azure DevOps, and GitHub Actions secrets immediately.\n- Enable secret scanning and anomalous credential-use alerts in your cloud environments to detect stolen credentials in use.\n\n**Long-term improvements:**\n- Integrate software composition analysis (SCA) tools into your CI\u002FCD pipeline to flag newly introduced or updated dependencies before they reach production.\n- Establish an internal package mirror or artifact proxy (e.g., Artifactory, Nexus) so all third-party packages are reviewed and cached before developer use.\n- Apply least-privilege principles to CI\u002FCD pipeline credentials so that stolen secrets have minimal blast radius.\n\n**Detection measures:**\n- Monitor PyPI (or your package mirror) for unexpected version changes to critical dependencies using tools like `pip-audit` or Dependabot alerts.\n- Implement runtime behavioral monitoring to detect unexpected network calls or credential file access occurring at Python interpreter startup.",[12,13,14,15,16],"MITRE ATT&CK T1195.001: Compromise Software Dependencies and Development Tools","CIS Control 2: Inventory and Control of Software Assets","NIS2 Article 21(2)(d)","NIST SP 800-53 SA-12: Supply Chain Protection","OWASP A06:2021 Vulnerable and Outdated Components",{"NIS2 Article 21(2)(d)":18,"NIST SP 800-53 SA-12: Supply Chain Protection":19,"OWASP A06:2021 Vulnerable and Outdated Components":20,"CIS Control 2: Inventory and Control of Software Assets":21,"MITRE ATT&CK T1195.001: Compromise Software Dependencies and Development Tools":22},"NIS2 Article 21(2)(d) mandates supply chain security measures, including controls over the security of third-party software dependencies, which would have required vetting packages like agent-framework before use.","SA-12 requires organizations to implement protections against supply chain threats, including integrity verification of third-party software components acquired from public repositories.","This OWASP category covers the risk of using unverified or compromised third-party components, which is precisely the attack vector exploited by the malicious PyPI releases.","CIS Control 2 requires organizations to track and allowlist authorized software, which would have flagged the unexpected version change in agent-framework before it was executed in production.","This technique specifically covers adversaries inserting malicious code into third-party libraries distributed via public package managers like PyPI, which is exactly how the credential stealer was delivered.","published","2026-11-17T23:21:25.110086+00:00","2026-11-17T23:21:25.099+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.aikido.dev\u002Fblog\u002Ftwo-malicious-agent-framework-releases-hit-pypi-in-33-minutes","two-malicious-agent-framework-releases-hit-pypi-in-33-minutes-513557","Two malicious agent-framework releases hit PyPI in 33 minutes",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[],[45,49,52],{"slug":46,"name":47,"problem":48},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":34,"name":50,"problem":51},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":53,"name":54,"problem":55},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]