Decompilers Are Meritocracy

One of the most educational tools of the decade is the Flash decompiler because it introduces consequences to people who previously enjoyed abstraction.

Some executive says we should hide the business logic in the SWF because nobody can read compiled files. This belief usually comes from the same generation that thought zip files were encryption.

Then a curious teenager or annoyed consultant decompiles the application and discovers internal endpoints, feature flags, forgotten admin screens, half-built products, verbose comments, and the occasional credential that should have died in development.

The decompiler does not create insecurity. It merely publishes the minutes.

I learned years ago to assume anything shipped to the client will be read eventually. If not by an attacker then by a competitor. If not by a competitor then by a bored employee. If not by them then by me six months later asking why I wrote any of it.

So I keep secrets server side. I keep privileged decisions server side. I keep my dignity wherever possible, though the platform offers limited storage for that given the onslaught of security advisories in the Adobe environments.

Still, every quarter someone rediscovers magical thinking.

Can we obfuscate it? Yes. You can also write your PIN on paper in cursive.

Can we encrypt the requests? Transport already exists. Your problem is trust, not punctuation.

Can we disable right click? Certainly. Nothing terrifies determined attackers like inconvenience.

The decompiler is the fairest person in the room. It judges everyone equally and rewards honesty.

Popular posts from this blog

The Fallacy of Cybersecurity by Backlog: Why Counting Patches Will Never Make You Secure

By a Former Engineer Turned Cybersecurity Leader For much of my twenty years as a software and security engineer, and now as a cybersecurity executive, I have watched organizations cling to a deeply flawed belief: that security maturity is reflected in the length of the patch backlog, the volume of vulnerabilities closed, or the number of tickets resolved in a quarter. Entire cultures are built around these metrics. Dashboards glow green when patch counts dip. Leaders celebrate the deletion of Jira, SNOW, etc. tickets as if the act of closing them somehow hardened the enterprise. But this fixation on downstream remediation creates an illusion of control while masking the fundamental problem upstream, there is an innovation pipeline that lacks guardrails, architectural clarity, and secure defaults. The symptom becomes the scorecard, and the root cause remains untouched often under a guise of promoting freedom. Security teams often find themselves in a perpetual treadmill of “forever f...
Read more

IPv6 White Paper I: Primer to Passive Discovery and Topology Inference in IPv6 Networks Using Neighbor Discovery Protocol

Introduction IPv6 drastically reshapes the surface of network reconnaissance, replacing the narrow 32-bit address space and broadcast semantics of IPv4 with expansive subnets and a multicast-centric control architecture. In this new model, Neighbor Discovery Protocol (NDP), Multicast Listener Discovery (MLD), and ICMPv6 signaling collectively define how hosts announce their presence, interact with routers, form addresses, resolve local neighbors, and verify reachability. Although this model was engineered for efficiency and stateless configuration, its reliance on predictable multicast traffic introduces a rich layer of metadata that can be quietly harvested by a passive observer. This paper explores the extent to which NDP, and its associated control protocols, leaks meaningful information about a network’s hosts, topology, addressing structure, and operational state. It also outlines how these behaviors can be transformed into the foundation of a silent IPv6 reconnaissance system cap...
Read more

This is Cybermancy

Image
Preface This document is a manifesto, not a tutorial. It is written for practitioners who live inside systems rather than around them. It is for those who build, test, trace, break, and repair complex machinery at scale. It is not concerned with tools, techniques, or exploits, but with the way of seeing that precedes all of them. The worldview here is neither criminal nor romantic albeit a bit poetic and whimsical in my own way. It is operational. It emerges naturally in those who understand that modern systems fail not because they are attacked, but because they are misunderstood. What follows is a statement of posture, responsibility, and discipline for those who recognize that sight itself is the rarest capability on the Grid. Cybermancers are not defined by exploits, hardware, or street legend. Those tangentials  are the residue and not the essence. A cybermancer is defined by how they see the Grid  not as fortresses, maps, gates, and walls, but as a breathing lattice of...
Read more