AI and Tech Summaries - AI Weekly Malaysia

Summaries

Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.

Window

Today Yesterday This week Last week This month Last month All time

Showing 1-1 of 1 results

Date	Provider	Score	Summary
28 Sep 2026, 7:00 PM	Tom's Hardware	6.5	Teenager hacks open Microsoft database with 17 trillion total rows and 25,000 user accounts Tom's Hardware reports that a teenager accessed an open Microsoft database containing 17 trillion total rows and 25,000 user accounts, reportedly by pairing a custom AI bot with a failure to validate JWT tokens, and earned a $5,000 bug bounty. The article body available here is almost entirely paywall and newsletter boilerplate, so the mechanics of the attack, the affected service, and Microsoft's response are not described in the text provided. Why: The one concrete technical claim is 'lack of JWT token validation' — if your app accepts a JWT without verifying its signature and claims, an attacker can mint their own token and read whatever the database returns, which is exactly the class of mistake that ships when auth is generated quickly and never tested. Before your next deploy, confirm your backend actually verifies the signing key and issuer rather than decoding the token payload, and check that any AI-generated auth code isn't doing `jwt.decode` where it should be doing `jwt.verify`. security jwt bug-bounty ai-agents authentication

Date

Provider

Score

Summary

28 Sep 2026, 7:00 PM

Tom's Hardware

6.5

Teenager hacks open Microsoft database with 17 trillion total rows and 25,000 user accounts

Tom's Hardware reports that a teenager accessed an open Microsoft database containing 17 trillion total rows and 25,000 user accounts, reportedly by pairing a custom AI bot with a failure to validate JWT tokens, and earned a $5,000 bug bounty. The article body available here is almost entirely paywall and newsletter boilerplate, so the mechanics of the attack, the affected service, and Microsoft's response are not described in the text provided.

Why: The one concrete technical claim is 'lack of JWT token validation' — if your app accepts a JWT without verifying its signature and claims, an attacker can mint their own token and read whatever the database returns, which is exactly the class of mistake that ships when auth is generated quickly and never tested. Before your next deploy, confirm your backend actually verifies the signing key and issuer rather than decoding the token payload, and check that any AI-generated auth code isn't doing `jwt.decode` where it should be doing `jwt.verify`.