
The Dangers of eval: A Cautionary Tale
A deep dive into why eval and its cousins (new Function, setTimeout(string)) are dangerous, illustrated with real-world-style examples and concrete mitigations for web and Node.js applications.

A deep dive into why eval and its cousins (new Function, setTimeout(string)) are dangerous, illustrated with real-world-style examples and concrete mitigations for web and Node.js applications.
High-profile incidents involving JavaScript-ranging from self-propagating XSS worms to supply-chain malware and third‑party script skimmers-offer urgent lessons for modern web developers. This article analyzes notable breaches, explains what went wrong, and gives a practical security checklist for preventing similar failures.
A deep dive into whether JavaScript frameworks should ship with stronger security defaults. We weigh responsibility, developer experience, technical trade-offs, and practical steps frameworks can take to be secure-by-default without crippling productivity.

Popular JavaScript libraries and frameworks speed development - but they also carry subtle, damaging security risks: supply‑chain attacks, prototype pollution, XSS from HTML/Markdown parsers, and dangerous framework APIs. This article explains concrete examples (event-stream, jQuery/lodash prototype pollution, Markdown/XSS issues), how these attacks work, and a practical, prioritized playbook to protect your apps.

A practical, in-depth guide to advanced JavaScript security for 2024: cutting-edge sanitization techniques, runtime protections, supply-chain hardening, and secure-coding patterns that go beyond the usual recommendations.