Despite some health problems #flareon11 is finally in the bag! A big mental block on challenge 9 stumped me for days while the solution was in front of me all time. Very interesting but also way too long. Luckily 5, 7 and 10 were awesome and very well designed. Onto next year!

Contribute to open source, learn through self-education or courses, record educational podcasts, or grow your pet project easily with a FREE Rider subscription for non-commercial development. Download and start today 👉 jb.gg/rd-free Spread the word! #dotnet #gamedev

I just published my writeups for all challenges of #flareon11: 👉 washi1337.github.io/ctf-writeups/w… 👉 blog.washi.dev/posts/flareon1… Hope you like them as much as I liked writing them!

finally found some time to publish my writeup for flare-on 11's level 9 challenge -- serpentine! also wrote a secondary post to go along with it out of fascination on how x64 Windows SEH works under the hood :) blog.elmo.sg/posts/flareon-… blog.elmo.sg/posts/posts/st…

I did a project on making an optimized implementation of the S+ tree. The result is 40x speedup over plain binary search! It builds on Algorithmica's post on S-trees and the famous paper "Array layouts for comparison based searching" by Paul Khuong ([email protected]). 🧵 curiouscoding.nl/posts/static-s…

#AsmResolver 6.0.0-beta.2 has been released This is a maintenance release that addresses many regressions introduced by the refactors in 6.0.0-beta.1. Get it on NuGet or GitHub 👉github.com/Washi1337/AsmR…

Ghidra 11.3 has been released! github.com/NationalSecuri…

#AsmResolver 6.0.0-beta.3 just got pushed to NuGet! More bugs were found and squashed. We are closing in on a full release with most of the public API being stable. Get it on GitHub or NuGet👉 github.com/Washi1337/AsmR… #dotnet #pe #reversing

After #flareon11 challenge 7, I got inspired to build tooling for #dotnet Native AOT reverse engineering. As such, I built a #Ghidra Analyzer that can automatically recover most .NET types, methods and frozen objects (e.g., strings). Blog:👉blog.washi.dev/posts/recoveri…

Y'all at Malware Village were awesome! I really was not expecting the warm welcome that I got 😅 Maybe (hopefully!) till next #defcon (or at wherever-con)!

#flareon12 is coming in hot and fast this year and will only run for 4 weeks this year instead of the usual 6. Don't miss it! flare-on.com

#AsmResolver 6.0.0-beta.4 released! This release addresses many shortcomings found during beta.3, including ARM32 and ARM64 support, auto references importing, and many other DX improvements. 👉 Get it on GitHub or NuGet: github.com/Washi1337/AsmR… #dotnet #pe #reversing

FLARE-On 12 is about to blow up your weekends: security.googlecloudcommunity.com/news-announcem… #flareon12

Yikes, seems someone screwed up and started #flareon12 early. Challenges were public for some hours. They are closed again but 200 players are already a couple challenges in early. This seems unfair to the people that compete for the top. Any comments @mandiant nickharbour ?

Timezones are hard, FLARE-On is harder! Apologies, challengers – #flareon12 had an unintentional early start. To keep things fair for everyone, we are pausing the competition. We're evaluating the situation and will provide an update around 10 AM ET.

Unfortunately, the #flareon12 unlocked early yesterday and some players got a head start. This will not effect the final standings as deltas will be applied to the player's final solve times (if they finish) to reflect the early access they received.

#flareon12 finally in the bag. What a rollercoaster ride challenge 9 was. Reminded me of a certain reoccurring DEFCON CTF challenge, iykyk :) A bit sad that chall 7 was the only one that really felt it was malware related, but nonetheless, I immensely enjoyed this year!

A reoccurring question I keep seeing in my DMs (also during this #flareon12) is "hey I tried [insert LLM model] but it didn't work. Now what?". It's unsettling to me. If (security) people can't think or do research themselves anymore, I think we're gonna have a problem.