Monday,
June 01, 2026

🥖 Palette Cleanser

The best cloud security conference of the year, fwd:cloudsec North America, kicks off today in Washington. If you are not in the room, the talks stream live across two rooms each day, June 1 Room 1, June 1 Room 2, June 2 Room 1, and June 2 Room 2. AWS security content has slowed to a trickle these last few weeks, so the timing could not be better. With this much fresh research about to land on stage, the next few issues should have a lot more to chew on.

Since issue 251 we have tracked the TeamPCP supply-chain campaign that hijacked the Trivy scanner and cascaded through KICS, LiteLLM, and Telnyx, but we never named one of its biggest victims. CERT-EU's April 2 post-mortem provides detail on how they got pwned. A single AWS API key, lifted through the poisoned Trivy build chain on March 19, was enough to breach the AWS account behind Europa's web hosting, and ShinyHunters dumped 350GB spanning 42 Commission entities and dozens of other EU bodies. CERT-EU notes the stolen key also carried management rights that could have reached other Commission AWS accounts, though there is no evidence the attackers went that far. We are circling back now because it is the clearest reminder yet of where these campaigns actually land. In a connected org, one leaked key from one trusted dev tool can turn a single account into an organization-sized blast radius.

Have feedback about AWS Security Digest? Tell us here. This issue is also available to share online.

📋 Chef's selections

  • Zapocalypse: The Attack Chain That Could Have Hijacked Zapier by Yair Balilti

    Yair started with nothing but a free Zapier account that lets you run Python, and chained it into a working path to code execution in every authenticated Zapier user's browser. The pivot that should scare you is he pulled leftover AWS session tokens straight out of the Lambda process's own memory via /proc/self/mem, used them to read ECR, and found an npm publish token buried inside a container image he pulled down. No zero-day anywhere, just five ordinary AWS misconfigurations stacked into a chain, and the writeup walks every step with the actual scripts.

  • Adding Strands Security Agents to Shadow Asset Scanner by Sena Yakut

    Sena keeps shipping practical AWS security tooling in the open. Most scanners just dump a list of misconfigurations, but here she keeps the plain boto3 scanner and layers AWS's open-source Strands agents on top, so it correlates the raw findings into actual attack chains and explains which ones matter. This is a good hands-on look at what an AWS-native security agent looks like in practice.

🥗 AWS security blogs

🍛 Reddit threads on r/aws

💸 Sponsor shoutout

Pleri logo

Meet Pleri: your AI security engineer. She’s not a chatbot. Pleri proactively finds meaningful security work and fixes issues before they become problems.

Learn more about Pleri and see her in action.

🤖 Dessert

Dessert is made by robots, for those that enjoy the industrial content.

🧁 IAM permission changes

🍪 API changes

🍹 IAM managed policy changes

☕ CloudFormation resource changes

    No resource updates this week.

🎮 Amazon Linux vulnerabilities

📺 AWS security bulletins

    No bulletins this week.

🚬 Security documentation changes

YouTube Twitter LinkedIn

Crafted with ❤️ by Plerion. We simplify cloud security.