[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fmRLR819L2a5FFSucSYYWw6P-qpYBkNv3Zo1hk4J_ttc":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"status":20,"created_at":21,"published_at":22,"article":23,"tags":27,"podcasts":46},"8db27106-2d34-4e09-a1e1-55eba28b36cb","ai-coding-assistants-enable-slopsquatting-supply-chain-attacks-at-machine-speed","c0160572-d59f-40da-9dbb-ca2ea42f14b5","AI Coding Assistants Enable 'Slopsquatting' Supply Chain Attacks at Machine Speed","AI coding assistants can hallucinate non-existent open source package names, which attackers proactively register with malicious payloads — a technique dubbed 'slopsquatting.' Because AI generates code at machine speed, these unvetted dependencies can enter codebases far faster than traditional security reviews can catch them. This represents a novel supply chain risk where the attack surface is amplified by automation rather than human error alone. Organizations that blindly trust AI-suggested dependencies without verification are effectively outsourcing package vetting to a system that has no awareness of malicious intent. The consequences range from data exfiltration to full supply chain compromise affecting downstream users.","**Immediate actions:**\n- Audit all AI-assisted code commits for unverified or newly introduced open source dependencies before merging.\n- Cross-reference every AI-suggested package against authoritative registries (e.g., PyPI, npm) to confirm the package exists and matches expected metadata.\n\n**Long-term improvements:**\n- Implement a software composition analysis (SCA) tool in CI\u002FCD pipelines to automatically flag unknown, suspicious, or newly registered packages.\n- Establish an internal approved-package allowlist and require formal review before any new dependency is introduced into production code.\n- Train developers on slopsquatting risks and enforce policies governing acceptable use of AI coding assistants in security-sensitive workflows.\n\n**Detection measures:**\n- Monitor dependency manifests (e.g., package.json, requirements.txt) for unexpected changes using version-controlled diff alerts.\n- Integrate threat intelligence feeds that track newly registered or typosquatted packages in major open source registries.",[12,13,14,15,16,17,18,19],"CIS Control 2: Inventory and Control of Software Assets","CIS Control 16: Application Software Security","NIST SP 800-161r1: Supply Chain Risk Management","NIST SSDF PW.4: Reuse Existing, Well-Secured Software","NIST CSF ID.SC-3: Supply Chain Risk Management","SLSA Supply Chain Levels for Software Artifacts (Framework)","OWASP A06:2021 – Vulnerable and Outdated Components","ISO\u002FIEC 27036: Information Security for Supplier Relationships","published","2026-08-13T16:20:48.573976+00:00","2026-08-13T16:20:48.291+00:00",{"id":7,"url":24,"slug":25,"title":26},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fwho-vets-ais-code-the-scale-challenge-facing-open-source-ingestion\u002F","who-vets-ai-s-code-the-scale-challenge-facing-open-source-ingestion-93f55e","Who Vets AI’s Code? The Scale Challenge Facing Open Source Ingestion",[28,34,40],{"id":29,"name":30,"slug":31,"description":32,"color":33},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":35,"name":36,"slug":37,"description":38,"color":39},"7261eb8f-acd4-4d93-a489-7fdd652ec0ea","Security Awareness","security-awareness","Phishing, social engineering, human error","#22c55e",{"id":41,"name":42,"slug":43,"description":44,"color":45},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[]]