

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://blog.washi.dev/</id>
  <title>Washi</title>
  <subtitle>A blog about my programming and reverse engineering adventures.</subtitle>
  <updated>2026-05-31T11:16:30+00:00</updated>
  <author>
    <name>Washi</name>
    <uri>https://blog.washi.dev/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://blog.washi.dev/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://blog.washi.dev/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Washi </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Why Custom Attributes in .NET give me Nightmares</title>
    <link href="https://blog.washi.dev/posts/custom-attributes-and-why-they-suck/" rel="alternate" type="text/html" title="Why Custom Attributes in .NET give me Nightmares" />
    <published>2026-05-30T00:00:00+00:00</published>
  
    <updated>2026-05-31T00:00:00+00:00</updated>
  
    <id>https://blog.washi.dev/posts/custom-attributes-and-why-they-suck/</id>
    <content type="text/html" src="https://blog.washi.dev/posts/custom-attributes-and-why-they-suck/" />
    <author>
      <name>Washi</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  <summary>Some people may think I am a shill for .NET.  With my previous post, they may be right.  However, as much as I like .NET, there are some things that just really do not make any sense to me, and they frustrate me to no end.  Given that I maintain a PE parsing library and thus am deeply familiar with the anatomy of .NET binaries, I feel I am qualified to complain about some of the design choices ...</summary>

  </entry>

  
  <entry>
    <title>Addressing Common Misconceptions about .NET in the InfoSec World</title>
    <link href="https://blog.washi.dev/posts/misconceptions-about-dotnet/" rel="alternate" type="text/html" title="Addressing Common Misconceptions about .NET in the InfoSec World" />
    <published>2026-02-21T00:00:00+00:00</published>
  
    <updated>2026-02-21T00:00:00+00:00</updated>
  
    <id>https://blog.washi.dev/posts/misconceptions-about-dotnet/</id>
    <content type="text/html" src="https://blog.washi.dev/posts/misconceptions-about-dotnet/" />
    <author>
      <name>Washi</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  <summary>Over the past couple years, I have come to know the .NET platform pretty well, from both a developer’s and a reverse engineer’s standpoint.  I can’t always quite say the same about people in the security community.  In fact, more often than not, I encounter a lot of “experts” in the scene (e.g., on Twitter, YouTube, forums, blogs, webinars, talks, chat logs…) that come up with factoids about .N...</summary>

  </entry>

  
  <entry>
    <title>Flare-On 12 Write-Ups</title>
    <link href="https://blog.washi.dev/posts/flareon12/" rel="alternate" type="text/html" title="Flare-On 12 Write-Ups" />
    <published>2025-12-23T00:00:00+00:00</published>
  
    <updated>2025-12-23T00:00:00+00:00</updated>
  
    <id>https://blog.washi.dev/posts/flareon12/</id>
    <content type="text/html" src="https://blog.washi.dev/posts/flareon12/" />
    <author>
      <name>Washi</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
    <category term="CTF" />
    
  

  <summary>At last, as promised in my previous post, with a huge delay I finally managed to finalize my Flare-On12 write-ups. Overall, it was a really good and fun set of challenges, and as always, the latter ones humbling me, reminding me how much I still have to learn in the field of RE.  My only main complaint: I wish there were more realistic/malware related challenges. This year felt very CTF-y :^). ...</summary>

  </entry>

  
  <entry>
    <title>Life Updates and Other Ramblings</title>
    <link href="https://blog.washi.dev/posts/life-update/" rel="alternate" type="text/html" title="Life Updates and Other Ramblings" />
    <published>2025-11-07T00:00:00+00:00</published>
  
    <updated>2025-11-07T00:00:00+00:00</updated>
  
    <id>https://blog.washi.dev/posts/life-update/</id>
    <content type="text/html" src="https://blog.washi.dev/posts/life-update/" />
    <author>
      <name>Washi</name>
    </author>

  
    
    <category term="Miscellaneous" />
    
  

  <summary>Today a bit of a different, more rambly post.  DEFCON and Grand Canyon  It’s been a couple of months since I’ve been back from BSidesLV 2025 and DEFCON 33. Long story short, it was awesome and extra special this year for me. I met so many cool and talented people that have humbled me in many ways. From the talks to the people (shoutout Malware Village), there is so much cool stuff around that I...</summary>

  </entry>

  
  <entry>
    <title>Recovering Metadata from .NET Native AOT Binaries</title>
    <link href="https://blog.washi.dev/posts/recovering-nativeaot-metadata/" rel="alternate" type="text/html" title="Recovering Metadata from .NET Native AOT Binaries" />
    <published>2025-04-18T00:00:00+00:00</published>
  
    <updated>2025-04-18T00:00:00+00:00</updated>
  
    <id>https://blog.washi.dev/posts/recovering-nativeaot-metadata/</id>
    <content type="text/html" src="https://blog.washi.dev/posts/recovering-nativeaot-metadata/" />
    <author>
      <name>Washi</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  <summary>Ever seen a binary that looks like a .NET binary based on its strings, but .NET decompilers are not able to open them?    .NET or not?  You may just be dealing with a Native AOT binary!  That may sound scary, native decompilation is much harder than .NET decompilation. However, what if you could make Ghidra look like this:    Ghidra Native AOT Extension  In this post, we will discuss Native AOT...</summary>

  </entry>

</feed>


