Jaswanth

Skills & Arsenal

timeline.reverse()

Posts

• Jun 25, 2026
  [+] BOP and ROP - Code Reuse Attacks
• May 27, 2026
  [+] Packers and Unpacking
• May 9, 2026
  [+] VM Obfuscation in Binary Protection
• Apr 22, 2026
  [+] From Curiosity To Cyber Security!
• Apr 1, 2026
  [+] Malware Analysis Techniques
• Mar 14, 2026
  [+] Decompiled Code Analysis
• Feb 6, 2026
  [+] When Trust Becomes the Vulnerability
• Jan 7, 2026
  [+] Getting Started with CTFs

Notes

• Every Binary Has a Story

  06/18/26, 08:20 AM

  When I open a binary in Ghidra, I remind myself - someone wrote this.

  They made choices. Why did they use this library? Why is this function inlined? Why is there a sleep call here? Why does this check exist?

  Those choices tell me about the developer, the deadline they were under, and sometimes the shortcuts they took.

  Reverse engineering is not just technical. It is understanding human decisions through the lens of machine code.

  The compiler optimized their intent. My job is to recover it.

• Automation Is Not a Replacement for Thinking

  06/05/26, 07:10 AM

  I automated my recon workflow. Nmap scans, directory brute-forcing, subdomain enumeration - all scripted.

  Then I hit a target where none of it worked. The vulnerability was in business logic, not in exposed ports or hidden directories.

  Automation handles the known. Thinking handles the unknown.

  I still automate the repetitive parts. But I stopped trusting that automation alone will find what matters.

  The scanner finds the door. You still have to figure out what is behind it.

• Reverse Engineering Is Reading, Not Writing

  05/28/26, 10:45 AM

  People think reverse engineering is about writing exploits. It is not.

  It is about reading. Reading assembly. Reading memory layouts. Reading control flow graphs. Reading what a compiler decided to do with someone else’s code.

  The better you read, the faster you understand. The faster you understand, the easier everything else becomes.

  I spent weeks trying to write before I learned to read. That was backwards.

  Now I spend 80% of my time reading and 20% acting on what I found. The results are better.

  Patience in reading pays off in precision when it matters.

• The Best Exploits Are Boring

  05/15/26, 08:30 AM

  Everyone wants to find the flashy zero-day. The reality is different.

  Most real-world compromises start with:

  • A default password that was never changed.
  • An S3 bucket left public.
  • An admin panel exposed without auth.
  • A service running as root for no reason.

  The best exploits are boring because they work every time.

  I stopped chasing complexity and started checking the basics first. The boring stuff gets you in faster than any CVE ever will.

  Defenders - fix the boring stuff first. Attackers are counting on you not to.

• Logs Tell Stories If You Read Them

  05/04/26, 04:00 AM

  Everyone sets up logging. Few actually look at what gets collected.

  A failed SSH attempt at 3 AM. A service account querying AD at odd hours. A new scheduled task that no one remembers creating.

  These are not bugs. They are breadcrumbs.

  The difference between a secure environment and a compromised one is often just someone paying attention to what the logs are saying.

  Collect less, read more. Focused logging beats noisy logging every time.