Where Hackers Go Hunting: Frontend Storage Security
summary
Frontend storage routinely exposes real exploits: attackers use DevTools and one-line console edits to flip a localStorage tokens flag and unlock premium features, change an isAdmin cookie to perform admin actions when backends lack checks, or grab API keys in client code to inject data and corrupt a database. Public examples include stolen Tesla access tokens, exposed coupon arrays in global variables, and a working local LLM poisoning proof‑of‑concept that exfiltrates full therapy sessions via crafted sessionStorage/tab isolation values.
AI-written summary · about
chapters (5)
- 0:00Introduction to frontend storage risks
- 2:37Overview of frontend storage types
- 13:25Real-world storage vulnerabilities
- 19:58AI era and local LLM threats
- 25:01Key takeaways and security lessons
related talks
33mHacking The Front-End
41mThe Insecurity Caused By Trusting Your Client-Side Storage
35mInside a hacker’s mind
19mCritical Security Mistakes in Frontend Applications
43mAttacking Modern Web Technologies
01h 01mHow hacking works - Web edition
28mOffensive and Defensive Strategies for Client-Side JS Security
40mHow to hack an Angular app?
