AI Weekly Malaysia

Beacon, a CRM provider serving 1,500+ charities, says an AWS access key likely exposed in public JavaScript build artifacts is the leading suspect in a July 27 breach. The attacker copied the entire customer database—including attachments—and probably downloaded it in readable form within 1 hour 27 minutes, despite data being encrypted at rest, because the compromised key allowed decryption. Beacon's logs cannot identify which specific records were exfiltrated.

Why: If you ship JavaScript bundles to browsers, scan your build artifacts for embedded cloud credentials before deployment—this incident shows that encryption at rest is meaningless when the access key that can decrypt it is sitting in a public JS file. Founders running SaaS on AWS should verify that IAM keys are never bundled into frontend assets and that CI/CD pipelines include secret-detection steps.

A researcher purchased the domain noreply.net and began receiving automated emails from companies that had hardcoded 'noreply@noreply.net' addresses into their systems, including messages containing secrets like password reset links and API credentials. The article details what was exposed and which companies were affected.

Why: If your app sends automated emails with secrets (reset tokens, API keys, 2FA codes) to a 'noreply' address on a domain you don't control, that domain can expire and be bought by anyone. Audit your codebase for hardcoded sender or recipient domains you don't own, especially common patterns like noreply.net, and switch to your own controlled domain.