<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/security/</link><description>Recent content in Security on Muhammad Nuh</description><generator>Hugo</generator><language>en-us</language><managingEditor>ikanlemas0@gmail.com (Muhammad Nuh)</managingEditor><webMaster>ikanlemas0@gmail.com (Muhammad Nuh)</webMaster><lastBuildDate>Thu, 22 Oct 2026 10:30:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>You Clicked "Accept All." Here's What You Just Agreed To.</title><link>https://hexrogue.github.io/blog/cookies-trackers-consent-banner/</link><pubDate>Thu, 22 Oct 2026 10:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cookies-trackers-consent-banner/</guid><description>&lt;p&gt;Somewhere on the page, a banner is waiting. It has two buttons. One says Accept All. The other says Manage Preferences, which is less a button than a threat with a font and a legal department.&lt;/p&gt;&#10;&lt;p&gt;You click Accept All because you want to read the article. You have now agreed to a data-processing arrangement involving companies you have never heard of, in countries you cannot point to on a map, for purposes described in a document written by someone paid by the word. The document is longer than the article. It is longer than the article&amp;rsquo;s source code. It may be longer than your attention span, which is currently being held together by caffeine and a deep-fried burrito with a death wish.&lt;/p&gt;</description></item><item><title>Decrypting your own WPA2 traffic in Wireshark</title><link>https://hexrogue.github.io/blog/decrypt-wpa2-traffic-wireshark/</link><pubDate>Fri, 11 Sep 2026 20:10:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/decrypt-wpa2-traffic-wireshark/</guid><description>&lt;p&gt;A monitor mode capture is mostly noise: beacons, management frames, and encrypted data you cannot read. It is the digital equivalent of taping a conversation through a wall and getting a very detailed recording of the wall.&lt;/p&gt;&#10;&lt;p&gt;Wireshark will decrypt your own WPA2 traffic if you give it the passphrase and the capture contains the handshake. Miss either one and you have a very expensive screensaver. The gap between those two conditions is where most people get stuck.&lt;/p&gt;</description></item><item><title>WPA3 SAE, without the fairy tales</title><link>https://hexrogue.github.io/blog/wpa3-sae-dragonfly-handshake/</link><pubDate>Sat, 01 Aug 2026 17:40:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wpa3-sae-dragonfly-handshake/</guid><description>&lt;p&gt;WPA3 has a reputation problem. Marketing calls it unhackable, forums call it broken, and both are wrong in useful ways. The honest version is narrower and more interesting: WPA3 kills the offline dictionary attack, which is the technique most people mean when they say their wifi got hacked.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/memes/meme-wpa3-fine.jpg" alt="This Is Fine dog meme: WPA3 is unhackable while transition mode quietly keeps WPA2 alive"&gt;&#10;&lt;figcaption&gt;Marketing says unhackable. Transition mode says hold my WPA2.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="the-thing-sae-removes"&gt;The thing SAE removes&lt;/h2&gt;&#10;&lt;p&gt;Start with what WPA2 gives an attacker. The passphrase becomes a key, the four-way handshake derives session keys, and the whole exchange is readable on the air. A recording contains everything needed to test guesses at home, at full speed, on a machine that never has to touch the network again. The cracker is not attacking your router. They are attacking a file.&lt;/p&gt;</description></item><item><title>BLE past advertising: GATT, bonding and why trackers work</title><link>https://hexrogue.github.io/blog/ble-beyond-advertising-gatt-and-trackers/</link><pubDate>Mon, 08 Jun 2026 13:35:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/ble-beyond-advertising-gatt-and-trackers/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/"&gt;The recon post&lt;/a&gt; stops where most Bluetooth writing stops: a device shouts small packets into the room and you write down its name and address. That is advertising, and it is the shallow half. The other half is what happens once two devices agree to talk.&lt;/p&gt;&#10;&lt;p&gt;Bluetooth is a toddler with a walkie-talkie. Advertising is the part where it shouts its name. GATT is the part where it hands you a three-ring binder and expects you to admire the tabs.&lt;/p&gt;</description></item><item><title>Sub-GHz primer: 433 MHz, weather stations and remote controls</title><link>https://hexrogue.github.io/blog/sub-ghz-primer-433mhz/</link><pubDate>Sun, 31 May 2026 15:20:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/sub-ghz-primer-433mhz/</guid><description>&lt;p&gt;Wifi and Bluetooth both live at 2.4 GHz. The rest of the cheap wireless world lives below 1 GHz, and the ESP32 cannot hear any of it. That is the entire reason the second half of this project exists, and the reason your cheap remote control can reach the garage while your phone gives up at the kitchen door. The setup deserves a primer before the hardware arrives.&lt;/p&gt;&#10;&lt;h2 id="why-below-1-ghz"&gt;Why below 1 GHz&lt;/h2&gt;&#10;&lt;p&gt;Lower frequencies go further and through more walls at the same power. A 433 MHz signal from a coin cell crosses a house; a 2.4 GHz signal from the same cell struggles with two walls. The trade is bandwidth, and these devices do not need bandwidth. A weather sensor sends twelve bytes every minute. A doorbell sends one bit when pressed. A lower frequency with a wide open band is the correct engineering choice, and it has been for thirty years.&lt;/p&gt;</description></item><item><title>Beacon spam: how the air fills with junk network names</title><link>https://hexrogue.github.io/blog/beacon-spam-and-the-wifi-list/</link><pubDate>Tue, 12 May 2026 09:05:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/beacon-spam-and-the-wifi-list/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/80211-frames-you-can-read/"&gt;A beacon&lt;/a&gt; is the simplest frame in wifi. A router announces its name about ten times a second, on its channel, to nobody in particular. It is unsigned, it is unencrypted, and any radio can transmit one.&lt;/p&gt;&#10;&lt;p&gt;Your phone treats that announcement like a guest list. No bouncer, no ID check, no guy named Chad at the door asking if you are on the list. Anyone with a radio can add a name. Copy that frame at scale and you have beacon spam.&lt;/p&gt;</description></item><item><title>Cracking your own password: from PMKID to hashcat</title><link>https://hexrogue.github.io/blog/cracking-your-own-password-pmkid/</link><pubDate>Wed, 29 Apr 2026 19:45:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cracking-your-own-password-pmkid/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/80211-frames-you-can-read/"&gt;The PMKID is a coat-check ticket&lt;/a&gt;: a blob the router hands out before any real authentication, derived from your wifi passphrase. This post is the other half, the part where the ticket becomes a password. On your own network, in your own lab, which is the only version of this that belongs on a blog. It is also the closest thing wifi has to a receipt that says &amp;ldquo;your password is probably fine, but let&amp;rsquo;s check.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Watching your own air: rogue access points and evil twins</title><link>https://hexrogue.github.io/blog/watching-your-own-air-rogue-aps/</link><pubDate>Tue, 07 Apr 2026 11:10:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/watching-your-own-air-rogue-aps/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/"&gt;Recon&lt;/a&gt; gives you a table of every radio in range. This post is about the one entry that should not be there.&lt;/p&gt;&#10;&lt;p&gt;It is the wifi equivalent of finding a second front door on your house, with a welcome mat that has your name on it.&lt;/p&gt;&#10;&lt;p&gt;A rogue access point is any access point that is not part of your inventory. There are two shapes of it. The boring one is a real access point, plugged into your network, that nobody documented, usually a spare router someone enabled because the wifi was slow. The interesting one is not on your network at all: it is a second radio wearing your network&amp;rsquo;s name, broadcasting to your devices, waiting for them to join it.&lt;/p&gt;</description></item><item><title>WPA2, WPA3 and PMF: what actually stops the attacks I wrote about</title><link>https://hexrogue.github.io/blog/wpa2-wpa3-pmf-what-stops-them/</link><pubDate>Tue, 31 Mar 2026 16:30:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/wpa2-wpa3-pmf-what-stops-them/</guid><description>&lt;p&gt;&lt;a href="https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/"&gt;The deauth post&lt;/a&gt; ends with a promise: the fix is management frame protection, and modern gear just ignores a forged eviction notice. That is the short version. The long version is that wifi security has two generations, and the reason half the networks you can see are still forged-frame food is a compatibility setting. This post is the part where the promise meets the router menu, and the router menu is a swamp.&lt;/p&gt;</description></item><item><title>Passive recon: what a listener learns without joining anything</title><link>https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/</link><pubDate>Sun, 15 Mar 2026 08:50:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/passive-recon-wifi-and-ble/</guid><description>&lt;p&gt;Your phone&amp;rsquo;s wifi chip has opinions. It only hands the operating system frames addressed to it or to the network it belongs to, and it drops the rest without ceremony. It is the digital equivalent of a bouncer who only lets in people on the list, and then someone shows up with a clipboard and a monitor-mode adapter. Promiscuous mode turns that filter off and keeps everything the radio can hear.&lt;/p&gt;</description></item><item><title>Deauth: the 26 bytes anyone can forge</title><link>https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/</link><pubDate>Fri, 06 Mar 2026 20:15:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/deauth-frames-anyone-can-forge/</guid><description>&lt;p&gt;A deauth frame is a wifi eviction notice. It says one thing: you are no longer associated with this network. Twenty-six bytes that prove nothing about who sent them.&lt;/p&gt;&#10;&lt;p&gt;That missing proof is the entire story. It is the bureaucratic version of a bouncer throwing you out and then handing you a form that says &amp;ldquo;we have no idea who did this.&amp;rdquo;&lt;/p&gt;&#10;&lt;h2 id="the-frame"&gt;The frame&lt;/h2&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;c0 00 &amp;lt;- frame control: management frame, subtype 12 (deauth)&#10;3a 01 &amp;lt;- duration, filler, ignored&#10;ff:ff:ff:ff:ff:ff &amp;lt;- address 1: the target. broadcast means everyone listening&#10;02:11:22:33:44:55 &amp;lt;- address 2: who sent it (supposed to be the access point)&#10;02:11:22:33:44:55 &amp;lt;- address 3: which network this concerns&#10;f0 ff &amp;lt;- sequence number&#10;02 00 &amp;lt;- reason code 2: previous authentication no longer valid&#10;&lt;/code&gt;&lt;/pre&gt;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/diagrams/deauth-frame-layout.svg" alt="Byte by byte layout of the 26 byte deauthentication frame"&gt;&#10;&lt;figcaption&gt;The whole 26 bytes, laid out. Six of them hold the sender's address, and none of them are proof that the sender is who they claim.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;The first byte pair &lt;code&gt;c0 00&lt;/code&gt; is the giveaway. The top bits of &lt;code&gt;0xc0&lt;/code&gt; say management frame, the rest say subtype 12. Disassociation is the sibling, subtype 10, byte &lt;code&gt;a0&lt;/code&gt;. Over the air the two look nearly identical and are used the same way.&lt;/p&gt;</description></item><item><title>I Taught a $5 Board to Sniff WiFi, Then Fought Its Driver</title><link>https://hexrogue.github.io/blog/esp32-recon-rig-driver-said-no/</link><pubDate>Mon, 12 Jan 2026 09:20:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/esp32-recon-rig-driver-said-no/</guid><description>&lt;p&gt;It started with an ESP32 plugged into my laptop and a simple question: what can this thing actually hear. It ended one long evening later with me disassembling a closed WiFi driver, downgrading an entire SDK for nothing, and learning more about 802.11 frames than any lecture ever taught me. The answer was &amp;ldquo;more than the driver wanted me to know,&amp;rdquo; which is how a five-dollar board turns into a vendetta. The board now runs a recon dashboard I built from scratch. This is the whole story, including the part where I was wrong in public.&lt;/p&gt;</description></item><item><title>I Pointed Shodan at My Own IP</title><link>https://hexrogue.github.io/blog/i-pointed-shodan-at-my-own-ip/</link><pubDate>Thu, 14 Aug 2025 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/i-pointed-shodan-at-my-own-ip/</guid><description>&lt;p&gt;Last month I searched for myself on the internet. Not my name. My IP address. What came back was a list of my open doors, written up neatly like a menu. It was the digital equivalent of finding your house listed on a tour guide, with photos of the unlocked windows. I had published myself and never noticed.&lt;/p&gt;&#10;&lt;h2 id="shodan-is-google-for-machines"&gt;Shodan is Google for machines&lt;/h2&gt;&#10;&lt;p&gt;Google indexes websites. Shodan indexes everything else: routers, cameras, servers, smart fridges with opinions. It knocks on every door on the internet, writes down who answers and what they say about themselves, and puts it in a search bar.&lt;/p&gt;</description></item><item><title>My Bank Locked Me Out for Typing Like a Human</title><link>https://hexrogue.github.io/blog/malaysian-banks-locked-me-out/</link><pubDate>Tue, 17 Sep 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/malaysian-banks-locked-me-out/</guid><description>&lt;p&gt;Let me say this first so nobody gets confused. Malaysia is great. Food is elite, Grab shows up in four minutes, my MyKad renews faster than most countries ship a parcel. Then there is online banking, which feels designed by someone who has never forgotten a password in their life.&lt;/p&gt;&#10;&lt;p&gt;I use a password manager. I am the good user, the exact person every security blog begs you to become. Last Tuesday I tried to pay a bill at 11 PM. The manager filled in a 20 character monster, I reached for Enter, and my finger landed on the backslash key sitting right next to it. Tried again. Backslash. Third time, same key, because at 11 PM my hand runs on autopilot. Three wrong tries. Account blocked. Not slowed down. Blocked. My reward for doing security correctly was getting locked out over a key that lives one centimeter from Enter.&lt;/p&gt;</description></item><item><title>The One-Number Bug That Leaked Orders</title><link>https://hexrogue.github.io/blog/idor-everyones-orders/</link><pubDate>Mon, 20 May 2024 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/idor-everyones-orders/</guid><description>&lt;p&gt;Some bugs crash your app. The scary ones politely hand you other people&amp;rsquo;s data. I found one of those in a test shop, and it took changing a single number. One number. No exploit kit, no hoodie, no dramatic typing. Just a URL with the confidence of a bad password.&lt;/p&gt;&#10;&lt;h2 id="what-is-an-idor-explained-with-lockers"&gt;What is an IDOR, explained with lockers&lt;/h2&gt;&#10;&lt;p&gt;Imagine school lockers. Yours is number 42. You ask the office &amp;ldquo;what is in locker 42&amp;rdquo; and they tell you. Now imagine you ask &amp;ldquo;what is in locker 43&amp;rdquo; and they tell you that too, no questions asked. That is an IDOR: a bug where the app checks who you are, but never checks whether the thing you asked for is yours.&lt;/p&gt;</description></item><item><title>A Four-Evening Crackme</title><link>https://hexrogue.github.io/blog/crackme-four-evenings/</link><pubDate>Mon, 27 Mar 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/crackme-four-evenings/</guid><description>&lt;p&gt;After years of CTFs, a tiny crackme that asks for a serial key should have been a one evening job. A friend sent it over and said it would take an hour. It took four. The friend was right about the hour. The other three were a personal problem.&lt;/p&gt;&#10;&lt;h2 id="evening-one-strings-and-false-confidence"&gt;Evening one: strings and false confidence&lt;/h2&gt;&#10;&lt;p&gt;I ran strings on it and found the success message in plain text. I felt like a genius for about ten minutes. Then I opened it in Ghidra and the decompiler gave me a wall of FUN_00101060. Years of experience, same first reaction every time. My confidence filed for divorce.&lt;/p&gt;</description></item><item><title>Everything in My First Binary Was Named FUN_00101060</title><link>https://hexrogue.github.io/blog/reversing-tips-beginners/</link><pubDate>Thu, 19 Jan 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/reversing-tips-beginners/</guid><description>&lt;p&gt;The first binary I opened looked like a city with no street signs. Ghidra handed me a map full of FUN_00101060 and expected me to navigate. The map was technically correct. So is a phone book with no names. I did what every beginner does: stared at it, changed nothing, and closed the laptop.&lt;/p&gt;&#10;&lt;p&gt;A few binaries later, I have a loop that works.&lt;/p&gt;&#10;&lt;figure&gt;&#10;&lt;img src="https://hexrogue.github.io/images/diagrams/reversing-workflow.svg" alt="Diagram of the reversing loop: run strings, rename what you understand, then let the debugger settle it"&gt;&#10;&lt;figcaption&gt;Strings, rename, debugger, then back around for another pass.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="start-with-strings-because-binaries-are-bad-at-keeping-secrets"&gt;Start with strings, because binaries are bad at keeping secrets&lt;/h2&gt;&#10;&lt;p&gt;The &lt;code&gt;strings&lt;/code&gt; command prints every readable piece of text inside a binary. Error messages, URLs, passwords someone forgot to hide. Half of beginner challenges fall over right here because the answer was sitting in plain text. Thirty seconds of work. Do this before anything clever.&lt;/p&gt;</description></item><item><title>How to Spy on Any Program (Legally)</title><link>https://hexrogue.github.io/blog/spy-on-any-program/</link><pubDate>Mon, 05 Dec 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/spy-on-any-program/</guid><description>&lt;p&gt;Every program lies about what it does. Not maliciously. It just never tells you the full story. The installer says &amp;ldquo;quick setup&amp;rdquo; while writing files in six directories. The app says &amp;ldquo;no account needed&amp;rdquo; while phoning three analytics servers. It is not a conspiracy. It is a filing cabinet with no labels and a lock you can pick with strace.&lt;/p&gt;&#10;&lt;p&gt;After years of CTFs, homelab mysteries, and malware curiosity, I built a method for interrogating any program until it confesses. Five layers, cheapest first. This is the post I wish existed when I started.&lt;/p&gt;</description></item><item><title>Radare2: The Terminal Gremlin That Reads Binaries</title><link>https://hexrogue.github.io/blog/radare2-ultimate-guide/</link><pubDate>Tue, 16 Nov 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/radare2-ultimate-guide/</guid><description>&lt;p&gt;Everyone told me to learn Ghidra. I learned the terminal gremlin instead. Ghidra is a cruise ship: big, comfortable, everything labeled. Radare2 is a jetski you assemble mid-ocean while it insults you. The jetski comes with a manual written in flags and a strong opinion about your free time. I use both now, but r2 is the one I reach for first, and this is the guide I wish existed when I started.&lt;/p&gt;</description></item></channel></rss>