---
title: "#security articles | Hashnode"
description: "All about security. Read the latest #security articles and tutorials on Hashnode."
url: "https://hashnode.com/tag/security"
---

Tag

# #security

14,577 posts · 2,312 followers

[Rokkhe](https://hashnode.com/@rokkhe) · [18h ago](https://hashnode.com/posts/optimizely-web-incident-third-party-javascript-lessons/6afc11086c5439a1f4430235)

### [The Optimizely Web incident: what happened, and what SaaS teams should test now](https://rokkhe.hashnode.dev/optimizely-web-incident-third-party-javascript-lessons?utm_source=hashnode&utm_medium=feed)

On 16 November 2026, malicious code reached visitors of 178 organisations through Optimizely Web. A sourced timeline, how the attack worked, how Optimizely contained it, and what to test on your own stack.

10 min read · [rokkhe.hashnode.dev](https://rokkhe.hashnode.dev/optimizely-web-incident-third-party-javascript-lessons?utm_source=hashnode&utm_medium=feed)

[Shota Yamazaki](https://hashnode.com/@simukappu) · [11h ago](https://hashnode.com/posts/the-difference-was-time-to-notice-japan-s-2026-cybersecurity-incidents-read-from-the-defender-s-side/6afc6e2723edee91d974a230)

### [The Difference Was Time to Notice: Japan's 2026 Cybersecurity Incidents, Read from the Defender's Side](https://blog.simukappu.com/the-difference-was-time-to-notice-japan-s-2026-cybersecurity-incidents-read-from-the-defender-s-side?utm_source=hashnode&utm_medium=feed)

365 unauthorized-access and ransomware cases disclosed in Japan, Aug–Oct 2026, by way in and time to notice. Most found late did not stop work.

18 min read · [blog.simukappu.com](https://blog.simukappu.com/the-difference-was-time-to-notice-japan-s-2026-cybersecurity-incidents-read-from-the-defender-s-side?utm_source=hashnode&utm_medium=feed)

[Ship-Ready](https://hashnode.com/@getshipready) · [38m ago](https://hashnode.com/posts/supabase-42501-permission-denied-for-table-after-the-oct-30-change-the-safe-fix/6afd07665bd692e12b89c5f4)

### [Supabase 42501 "permission denied for table" after the Oct 30 change: the safe fix](https://getshipready.hashnode.dev/supabase-42501-permission-denied-for-table-after-the-oct-30-change-the-safe-fix?utm_source=hashnode&utm_medium=feed)

Your app worked yesterday. You (or your AI tool) added a new table, and now every request to it fails with 42501. Nothing is broken. Supabase changed a default, and the fix takes one minute. But the f

4 min read · [getshipready.hashnode.dev](https://getshipready.hashnode.dev/supabase-42501-permission-denied-for-table-after-the-oct-30-change-the-safe-fix?utm_source=hashnode&utm_medium=feed)

[Abdus Salam](https://hashnode.com/@aheadkit) · [1h ago](https://hashnode.com/posts/java4shell-i-ran-the-published-trigger-on-a-vulnerable-jdk-it-did-not-fire/6afcff720207d48bb485e18a)

### [Java4Shell: I Ran the Published Trigger on a Vulnerable JDK. It Did Not Fire.](https://aheadkit.hashnode.dev/java4shell-i-ran-the-published-trigger-on-a-vulnerable-jdk-it-did-not-fire?utm_source=hashnode&utm_medium=feed)

The headline version of Java4Shell is simple: a malformed Base64 string, 64 A characters followed by =, corrupts memory in OpenJDK, and from there the researchers at Calif reached remote code executio

5 min read · [aheadkit.hashnode.dev](https://aheadkit.hashnode.dev/java4shell-i-ran-the-published-trigger-on-a-vulnerable-jdk-it-did-not-fire?utm_source=hashnode&utm_medium=feed)

[VEILVM](https://hashnode.com/@veilvm) · [1h ago](https://hashnode.com/posts/a-client-side-chatbot-or-support-widget-still-ships-its-prompts-and-routing-rules/6afcfb533047969d81cf31f1)

### [A client-side chatbot or support widget still ships its prompts and routing rules](https://veilvm.hashnode.dev/a-client-side-chatbot-or-support-widget-still-ships-its-prompts-and-routing-rules?utm_source=hashnode&utm_medium=feed)

Product teams like in-page assistants: a support bubble, a docs bot, a "ask our product" overlay. The fastest way to ship one is to keep retrieval, routing, and a system prompt close to the widget so

5 min read · [veilvm.hashnode.dev](https://veilvm.hashnode.dev/a-client-side-chatbot-or-support-widget-still-ships-its-prompts-and-routing-rules?utm_source=hashnode&utm_medium=feed)

[Pradipta Nanda](https://hashnode.com/@sp1dy) · [19h ago](https://hashnode.com/posts/mcp-and-connectors-one-engine-for-every-data-source/6afbf71d6f5a47e1c947c343)

### [MCP and Connectors: One Engine for Every Data Source](https://zeonai.hashnode.dev/mcp-and-connectors-one-engine-for-every-data-source?utm_source=hashnode&utm_medium=feed)

How a declarative, universal connector framework turns 'another integration' into a config file — and why that matters for security, enterprises, and the people who actually use the product.

8 min read · [zeonai.hashnode.dev](https://zeonai.hashnode.dev/mcp-and-connectors-one-engine-for-every-data-source?utm_source=hashnode&utm_medium=feed)

[Network Data Labs](https://hashnode.com/@networkdatalabs) · [7h ago](https://hashnode.com/posts/detect-known-vpn-traffic-in-express-and-fastapi-middleware/6afca5008a360161ad20bce1)

### [Detect Known VPN Traffic in Express and FastAPI Middleware](https://networkdatalabs.hashnode.dev/detect-known-vpn-traffic-in-express-and-fastapi-middleware?utm_source=hashnode&utm_medium=feed)

A developer’s walkthrough of VPN-traffic middleware in Express and FastAPI: flags as signals, not a hard block.

7 min read · [networkdatalabs.hashnode.dev](https://networkdatalabs.hashnode.dev/detect-known-vpn-traffic-in-express-and-fastapi-middleware?utm_source=hashnode&utm_medium=feed)

[VibeFoundry](https://hashnode.com/@vibefoundry) · [4h ago](https://hashnode.com/posts/we-audited-160-ai-mcp-packages-7-062-files-plus-3-open-source-cli-mcp-tools-to-fix-security-ui-slop-browser-qa/6afccdcfe38b06b44f4f1385)

### [We Audited 160 AI & MCP Packages (7,062 Files) — Plus 3 Open-Source CLI & MCP Tools to Fix Security, UI Slop & Browser QA](https://vibefoundry.hashnode.dev/we-audited-160-ai-mcp-packages-7-062-files-plus-3-open-source-cli-mcp-tools-to-fix-security-ui-slop-browser-qa?utm_source=hashnode&utm_medium=feed)

AI coding agents (Claude Code, Cursor, Windsurf, Copilot) let developers build full-stack web apps in hours, but they consistently leave behind three production blind spots: Security Vulnerabilities

2 min read · [vibefoundry.hashnode.dev](https://vibefoundry.hashnode.dev/we-audited-160-ai-mcp-packages-7-062-files-plus-3-open-source-cli-mcp-tools-to-fix-security-ui-slop-browser-qa?utm_source=hashnode&utm_medium=feed)

[Pablo Infante](https://hashnode.com/@pabloinfante) · [5h ago](https://hashnode.com/posts/no-you-didn-t-encrypt-the-password-a-developer-s-guide-to-hashing/6afcc96dca494fb1efb3c710)

### [No, you didn’t encrypt the password — a developer’s guide to hashing](https://toolonium.hashnode.dev/no-you-didn-t-encrypt-the-password-a-developer-s-guide-to-hashing?utm_source=hashnode&utm_medium=feed)

There's a sentence I've seen in code reviews, Slack threads, and more than one incident postmortem: "Don't worry, the passwords are encrypted." Nine times out of ten, they weren't encrypted — they wer

4 min read · [toolonium.hashnode.dev](https://toolonium.hashnode.dev/no-you-didn-t-encrypt-the-password-a-developer-s-guide-to-hashing?utm_source=hashnode&utm_medium=feed)

[GeekSpark](https://hashnode.com/@geeksaprk) · [13h ago](https://hashnode.com/posts/php2shell-the-node-js-brotli-flaw-patch-guide/6afc5262d66f5bfae737509e)

### [PHP2Shell & the Node.js Brotli Flaw: Patch Guide](https://geekspark.hashnode.dev/php2shell-the-node-js-brotli-flaw-patch-guide?utm_source=hashnode&utm_medium=feed)

On October 21, 2026, PHP and Node.js both shipped urgent security releases on the same day. On the PHP side, two critical flaws nicknamed PHP2Shell let an attacker run code on a web server without log

11 min read · [geekspark.hashnode.dev](https://geekspark.hashnode.dev/php2shell-the-node-js-brotli-flaw-patch-guide?utm_source=hashnode&utm_medium=feed)
