Armored Code is a publication about application security, alert fatigue, and building tools that focus on signal over noise.
NGINX Rift and PoolSlip expose dangerous memory corruption flaws inside one of the Internet’s most trusted reverse proxies, turning rewrite rules into a potential remote code execution surface. From long-lived heap bugs to new exploitation paths, the edge just became the attack surface.
Signal Engine 0.3.0 transforms raw security findings into structured, actionable insight. With clustering, deduplication, and risk-based hotspots, noise gives way to clarity. Less data to sift through, more signal to act on.
Soak is a zero-dependency Docker image that aggregates a curated set of open-source security scanners into a single, reproducible execution environment.
Turning security tool outputs into actionable insights is one of the biggest challenges for developers and security engineers. In this post, I’m sharing a minimal viable product (MVP) that takes Semgrep scan outputs and visualize
In the previous post, we saw how many security tools can “lie”: they don’t tell the full story, generate noise, and often leave teams with a false sense of security. But what happens after a vulnerability is reported? The story doesn’t get any better: most findings are misunderstood.
We live in a world where developers and security teams are drowning in alerts. Every scanner, every automated tool, every “security dashboard” promises to tell you what matters—but in reality, most of it is noise.
During my OSCE exam preparation I had to deal with shellcode writing experience where very few allower characters were available.
In order to monitor dawnscanner security scaner usage, I introduced in upcoming version 2.0.0, a telemetry system.
A couple of days ago, I was working on my exploit-writing routine as preparation for my upcoming OSCE examination.
During my OSCE journey I came across an interesting technique to jump backwards into the very beginning of the buffer injected on the vulnerable process.
