A technical retrospective on a decade of PHP memory-safety research, crediting original discoverers and maintainers while examining failure atomicity, re-entrancy, bailout recovery, and cross-request ownership.
Representative Foreword
After the Code, the Structure Remains
The representative foreword of this blog: security now fails less at finding issues than at absorbing, sustaining, and acting on what has already been found.
This essay frames the entire site first. The posts on technical analysis, method, and governance all start from this same problem statement.

Detection, Method, Governance
🔥 A Mind That Dissects Systems
🔥 Trust and Culture Beyond Technology
🔥 Code That Fixes, Not Just Runs
PHP Memory-Safety Research Notes (2016–2026): Discoverers, Root Causes, Fixes and Evidence
A source-based provenance map of PHP memory-safety findings from 2016 to 2026, crediting original researchers and maintainers while separating issue status, reproducibility, exploitability, and patch verification.
Before Blaming AI False Positives: The Security Debt of Generalist-Led Organizations
A Korean financial-sector AI code-analysis test reported 40–60% false positives. The deeper question is how technical expertise, validation workflows, budgets, and decision rights shape actual security outcomes.
Why Are the Costs and Risks of Cybersecurity So Widely Distributed Across the Private Sector?
Starting from the debate over criminal liability for CISOs, this post traces Internet commercialization, information asymmetry, responsibilization, security externalities, CVD, NIS2, the CRA, and Korea’s 2026 reforms to ask how cybersecurity responsibility has been distributed—and why it is now being rebalanced.
Re-reading the ARTEX Attacks on Korea's Financial Sector: AI Agents, Disposable VPS Infrastructure, and Non-Customer-Facing Systems
A detailed analysis of the ARTEX-linked attacks on Korea’s financial sector using public reporting, Shodan/Censys exposure data, anonymous-vps cross-checks, and observed IoCs. The focus is not just the AI tool itself, but disposable infrastructure, non-customer-facing business systems, LLM credential theft, and the defensive changes likely to follow.

Race Condition (TOCTOU) Remediation: What Actually Worked in a Real Stack
The same check-then-act race keeps appearing across services: purchase-limit bypass, one draw used by many requests, duplicate coupon cancellation, daily-reward overruns. I built a real stack (nginx + Tomcat×2 + shared Postgres + Redis) and measured which fix actually holds. Most of them need no Redis lock — just a DB conditional UPDATE and an affected-rows check.

You Cannot Assess the Security of External SDKs by Checking Cryptographic Algorithms Alone
Algorithm names like AES-256 or TLS reveal nothing about how keys are generated, who controls the endpoint, or whether a response binds to the real transaction. A broader, evidence-based assessment model for external SDKs and native binaries.
Leak and Stage-2 Over One Socket: Reverse Single-Socket Staging
A malicious server corrupting a client that dials out to it, carrying both the libc leak and the second stage over one already-open socket in a single ROP chain. And why this is not a new pattern but a well-known composition.

Does Hiring the World's Best Hackers Improve Security?
Bringing world-class hackers and a CTF research ecosystem into an organization can make it stronger, but real security improvement requires turning offensive capability into governance and structural change.
Finding Vulnerabilities Is Not the Same as Building Attack Scenarios
A practical method for modeling vulnerabilities as attacker-relevant security state transitions and combining human intuition with bounded AI search
































