Researchers have revealed a sophisticated exploit sequence called “Zapocalypse,” showing how a seemingly restricted automation feature inside Zapier could have escalated into a widespread platform compromise. The chain reportedly started within “Code by Zapier,” where Python code executed inside an AWS Lambda container. Investigators confirmed that operating system commands were permitted, enabling deeper inspection of the runtime environment. Although temporary AWS credentials had supposedly been removed from environment variables, remnants still existed in process memory. By analyzing /proc/self/mem, the team successfully recovered leftover STS tokens, demonstrating that deleting references alone does not guarantee sensitive data is erased from memory during active execution. After obtaining the recovered credentials, researchers identified weaknesses in an IAM configuration tied to a role named allow_nothing_role. Despite its restrictive sounding name, the role granted enough permissions to enumerate Elastic Container Registry repositories and retrieve container layers. Further investigation uncovered a privileged NPM token embedded inside container build metadata rather than stored directly in the filesystem. The token reportedly bypassed two factor authentication requirements and possessed publishing access to internal Zapier packages, including zapier-design-system. Because this package was loaded into authenticated browser sessions, attackers theoretically could have inserted malicious JavaScript capable of hijacking user activity, modifying workflows, or abusing existing integrations connected to customer accounts. The findings also described another security concern involving a hardcoded Zapier Actions MCP credential located within a LiteLLM associated container. Researchers stated that the credential authenticated as a legitimate user and could perform sensitive operations such as sending emails through connected services. Zapier responded quickly after receiving the disclosure, revoking exposed tokens, tightening registry permissions, and implementing remediation measures within weeks. The researchers earned the program’s highest bug bounty reward of three thousand dollars. Beyond the immediate technical flaws, the incident highlights larger security challenges surrounding runtime isolation, cloud permissions, secret management, and software supply chain security, where several minor weaknesses combined into a potentially severe platform wide threat.
Charter Communications has confirmed a cybersecurity incident impacting millions of customers following a breach allegedly conducted by the ShinyHunters extortion gang. According t...
A critical Remote Code Execution (RCE) vulnerability has been identified in Samba, the widely used open-source SMB/CIFS file-sharing software for Linux and Unix systems. The flaw c...
A sophisticated cyber-espionage campaign linked to the Iran-aligned threat group Seedworm has targeted at least nine organizations across multiple countries during early 2026. The ...