I couldn't have said it better myself we just spent some time last week talking about shai halud happening again here we are more package compromises i'm kind of drilling through the different reports kind of that are being listed here you know team pcp there's an article here from all the way back in march which i think we covered back we covered back then brand new updates on the supply chain attacks happening trivi like llm so on and so forth folks the really big takeaway here is chris and i can can kind of name these different packages and libraries every week but in reality we've got to get good secure package management processes in place it's going to be critical to avoiding or mitigating or minimizing these types of attacks because chris to your point it's super easy just go register and develop and build a package put some malicious code inside of there someone somewhere sinks

Of traditional indicators such as poor documentation or repeated code patterns the company also highlights slop squatting where attackers register non-existent package names hallucinated by ai coding assistants hoping developers or autonomous agents will later install them amazon expects attackers to increasingly target ai-based security using malicious packages in the user's security systems themselves malicious packages could contain indirect prompt injection hidden in comments readme files dock strings or test fixtures designed to convince ai code scanners to mark malicious software as safe or ignore specific files amazon argues that defenders therefore need to analyze package behavior and dependency interactions rather than relying solely on isolated package scans and static signatures yeah i mean i think this is the new normal these supply chain attacks are getting more