<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://machinecase.com.br/</id><title>MachineCase</title><subtitle>macOS security researcher focused on malware analysis, reverse engineering, and threat hunting. Author of the SEA Analyzer Binary Ninja plugin.</subtitle> <updated>2026-05-25T12:10:21-03:00</updated> <author> <name>Felipe Romano</name> <uri>https://machinecase.com.br/</uri> </author><link rel="self" type="application/atom+xml" href="https://machinecase.com.br/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://machinecase.com.br/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Felipe Romano </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Reversing dart compile exe on macOS: Bringing blutter to Dart Standalone AOT Binaries</title><link href="https://machinecase.com.br/posts/dart-reverse-macos/" rel="alternate" type="text/html" title="Reversing dart compile exe on macOS: Bringing blutter to Dart Standalone AOT Binaries" /><published>2026-05-24T05:27:00-03:00</published> <updated>2026-05-25T12:09:51-03:00</updated> <id>https://machinecase.com.br/posts/dart-reverse-macos/</id> <content type="text/html" src="https://machinecase.com.br/posts/dart-reverse-macos/" /> <author> <name>Felipe Romano</name> </author> <category term="Malware Analysis" /> <category term="Security Research" /> <summary>The problem You receive a suspicious macOS binary that opens in Binary Ninja as thousands of anonymous stripped functions with no relevant imports, no readable strings, and no obvious entry point, and when you run strings all you get is libSystem, some pthread calls, and standard libc with nothing that explains what the binary actually does. Then you notice something: $ strings ./binary | gre...</summary> </entry> <entry><title>Defense Evasion via Single Executable Applications (SEA) in Node.js</title><link href="https://machinecase.com.br/posts/sea-node-defenseEvasion/" rel="alternate" type="text/html" title="Defense Evasion via Single Executable Applications (SEA) in Node.js" /><published>2026-05-10T10:37:00-03:00</published> <updated>2026-05-10T17:04:04-03:00</updated> <id>https://machinecase.com.br/posts/sea-node-defenseEvasion/</id> <content type="text/html" src="https://machinecase.com.br/posts/sea-node-defenseEvasion/" /> <author> <name>Felipe Romano</name> </author> <category term="Malware Analysis" /> <category term="Security Research" /> <summary>What is SEA (Single Executable Applications)? When a threat actor chooses Node.js SEA to deliver a payload, they are not making a development decision. They are making a detection decision. Node.js SEA was built to solve a legitimate problem: packaging an entire application into a single self-contained binary, with no requirement for the target to have a runtime installed. What lands on disk ...</summary> </entry> </feed>
