It’s a TDL3 sample btw. Having fun getting my ass handed to me. Will share different phases of the project, first will be sharing papers I’ve read on it. Will do a writeup on what I could infer from them, and discuss basic windows stuff related to it. We in for a long 2026.🥹🤣🤣

Washing the dishes doesn't exercise your brain or deepen your understanding of the problem. Solving technical problem by yourself does. Once you stop practicing, you loose the ability to think certain way, and you won't be good to even supervise the machine or question it. I am all for using LLMs, but let's be honest, promoting is too easy to even be called a skill. If this is our core education, humanity will degrade.

AI is cool and badass. I like it. No, it's not the end of the world. We can "contain" it. Now I will rant for a moment about what I dislike about AI. I strongly dislike when large corporations try to inject AI into every product, essentially forcing us to use AI. I also strongly dislike when people use AI for every small little thing in their life, such as leaving comments on websites like Xitter, YouTube, Reddit, etc. It defeats the entire purpose of leaving a comment on something... you're supposed to share YOUR thoughts, not an AI agents generated string output. It's goofy. I also strongly dislike the nonsense blabbering of AI propaganda, how it will destroy the world, or how companies need to "contain it", essentially acting as means to corner the AI model market, trying to strip it away from individuals who may want to host it locally. It's a facade of "Only WE can do AI, not YOU", whilst charging absurd fees for usage. I also dislike AI nerds who try to tell me to use AI to do things I do simply because I enjoy doing them. Yes, maybe an AI agent could reverse engineer faster than me, or code faster than me, but I do it because I enjoy it. AI is an excellent tool to enhance work flows, or learn (assuming it doesn't hallucinate). Okay, that's all I want to say about AI for today.

i'm back on the job market again - golang - mid level role - location flexible ⏰ pls rt for help ⏰

Totally agree, that's why I am planning to do this year's #FlareOn without using AI (unless there is a task where it's specifically required). The competitive side of the challenge may be dead, but we still can choose to have fun. Just like existence of a mountain lift doesn't have to kill the pleasure of climbing.

There is also a tutorial I wrote about how to make import recovery the most effective: hshrzd.wordpress.com/2025/03… - it also covers finding Original Entry Point (OEP) with the help of #TinyTracer

Time to time I see #malware unpacking tutorials using #PEsieve and *incorrectly* stating that it doesn't rebuild import table and you need to use external tools to do so. In fact it is just a matter of a commandline argument: /imp - documented on Wiki: github.com/hasherezade/pe-si…

My team at Elastic (Endpoint Protections) are hiring another Senior Security Research Engineer! If you are an avid Windows Internals and low level security enjoyer, & want to work with the best talent around - take a look! Feel free to drop me a dm! jobs.elastic.co/jobs/enginee…

My research blog about #JSCeal is finally out! It was quite a journey. I hope you will like it! // #V8 #bytecode #malware #deobfuscation

Learn everything

Simple rule: remember that anyone who tells you that it’s better to be ignorant just wants to sabotage you and/or enslave you

The related toolkit: github.com/hasherezade/jsc_d… ; More details on Wiki: github.com/hasherezade/jsc_d…

Thank you, @cursor_ai, for providing free credits to several FFmpeg developers. These credits will support their ongoing work on FFmpeg, including development and code review. We greatly appreciate Cursor’s support for FFmpeg and its community.

Compiled #V8 bytecode is still a niche #malware format, but it highlights a broader analysis problem: what happens when a payload falls between established toolchains? At #BlackHat2026, I’ll walk through the #JSCeal case study and the static deobfuscation toolkit I built to recover readable code. If you’ll be at #BlackHat, I’d be glad to see you there! blackhat.com/us-26/briefings…

Great insight and observation. 💙 therecord.media/a-conversati…

I've given my blog a slight lick of paint, if you are interested in offensive or defensive cyber engineering, check it out! I talk about malware development, EDR development, Windows Internals, and some misc reversing stuff :)) fluxsec.red/

remember when 512MB RAM was considered massive? programmers wrote code like every byte mattered. optimized everything. squeezed performance from nothing. suddenly nobody cared about efficiency anymore. just throw more RAM at it, problem solved. now we have 32GB RAM and Slack uses 2GB just to show text messages. Electron apps eat memory like it's free candy. we got better hardware and built worse software. abundance made us lazy.

New #TinyTracer (4.0) is ready: github.com/hasherezade/tiny_… - refactored for compatibility with the latest PIN - and with some new features!

C is not a low level language ACM Queue published this in 2018 and people are still arguing about it the idea is simple C was low level in 1972 when machines like the PDP-11 mapped code almost directly to instructions modern CPUs are completely different caches branch prediction SIMD out of order execution the C abstract machine cannot see or control most of that it cannot see the cache cannot express prefetching cannot directly control vectorization so performance depends on the compiler being smart enough to optimize the same argument C developers often criticize in higher level languages