<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://lipeozyy.github.io/</id><title>Ozyy</title><subtitle>malware analysis | reverse enginer </subtitle> <updated>2026-04-11T11:14:50+00:00</updated> <author> <name>Felipe</name> <uri>https://lipeozyy.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://lipeozyy.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://lipeozyy.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Felipe </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Toast phishing operations: Abusing Windows notifications for initial access</title><link href="https://lipeozyy.github.io/posts/Toast-Phishing-Operations-Abusing-Windows-Notifications-for-Initial-Access/" rel="alternate" type="text/html" title="Toast phishing operations: Abusing Windows notifications for initial access" /><published>2026-03-09T00:00:00+00:00</published> <updated>2026-03-09T00:00:00+00:00</updated> <id>https://lipeozyy.github.io/posts/Toast-Phishing-Operations-Abusing-Windows-Notifications-for-Initial-Access/</id> <content type="text/html" src="https://lipeozyy.github.io/posts/Toast-Phishing-Operations-Abusing-Windows-Notifications-for-Initial-Access/" /> <author> <name>Felipe</name> </author> <category term="Phishing" /> <summary>⚠️ Disclaimer | Educational Purpose Only This content is provided strictly for educational and research purposes. All techniques, concepts, and examples discussed in this post are intended to support the study of information security, malware analysis, and defensive research in controlled and legal environments. The author does not encourage, support, or condone the use of this materi...</summary> </entry> <entry><title>Reverse engineering a trojanized VSCode extension</title><link href="https://lipeozyy.github.io/posts/Reverse-Engineering-a-Trojanized-VSCode-Extension/" rel="alternate" type="text/html" title="Reverse engineering a trojanized VSCode extension" /><published>2026-03-09T00:00:00+00:00</published> <updated>2026-03-26T19:57:24+00:00</updated> <id>https://lipeozyy.github.io/posts/Reverse-Engineering-a-Trojanized-VSCode-Extension/</id> <content type="text/html" src="https://lipeozyy.github.io/posts/Reverse-Engineering-a-Trojanized-VSCode-Extension/" /> <author> <name>Felipe</name> </author> <category term="Malware" /> <summary>Introduction Hello everyone! Since it’s been a long time since I last brought a malware analysis or reverse engineering post, I’ve decided to share a very interesting case today. I’ve been researching something to showcase here and found a campaign where the artifact poses as a VS Code AI assistance extension. On the surface, it promises to be a “free” code generation assistant, but package ins...</summary> </entry> <entry><title>Windows Persistence (Part 1): Default file extension hijacking</title><link href="https://lipeozyy.github.io/posts/Windows-Persistence-(Part-1)-Default-File-Extension-Hijacking/" rel="alternate" type="text/html" title="Windows Persistence (Part 1): Default file extension hijacking" /><published>2026-03-09T00:00:00+00:00</published> <updated>2026-03-09T00:00:00+00:00</updated> <id>https://lipeozyy.github.io/posts/Windows-Persistence-(Part-1)-Default-File-Extension-Hijacking/</id> <content type="text/html" src="https://lipeozyy.github.io/posts/Windows-Persistence-(Part-1)-Default-File-Extension-Hijacking/" /> <author> <name>Felipe</name> </author> <category term="Persistence" /> <summary>⚠️ Disclaimer | Educational Purpose Only This content is provided strictly for educational and research purposes. All techniques, concepts, and examples discussed in this post are intended to support the study of information security, malware analysis, and defensive research in controlled and legal environments. The author does not encourage, support, or condone the use of this materi...</summary> </entry> <entry><title>Exploring the Kernel-Mode attack surface: Reverse engineering a vulnerable Driver abused to terminate EDRs</title><link href="https://lipeozyy.github.io/posts/Exploring-the-Kernel-Mode-attack-surface-Reverse-engineering-a-vulnerable-Driver-abused-to-terminate-EDRs/" rel="alternate" type="text/html" title="Exploring the Kernel-Mode attack surface: Reverse engineering a vulnerable Driver abused to terminate EDRs" /><published>2026-03-02T00:00:00+00:00</published> <updated>2026-03-02T00:00:00+00:00</updated> <id>https://lipeozyy.github.io/posts/Exploring-the-Kernel-Mode-attack-surface-Reverse-engineering-a-vulnerable-Driver-abused-to-terminate-EDRs/</id> <content type="text/html" src="https://lipeozyy.github.io/posts/Exploring-the-Kernel-Mode-attack-surface-Reverse-engineering-a-vulnerable-Driver-abused-to-terminate-EDRs/" /> <author> <name>Felipe</name> </author> <category term="Exploit" /> <summary>⚠️ Disclaimer | Educational Purpose Only This content is provided strictly for educational and research purposes. All techniques, concepts, and examples discussed in this post are intended to support the study of information security, malware analysis, and defensive research in controlled and legal environments. The author does not encourage, support, or condone the use of this materi...</summary> </entry> <entry><title>APC injection</title><link href="https://lipeozyy.github.io/posts/APC-injection/" rel="alternate" type="text/html" title="APC injection" /><published>2026-03-02T00:00:00+00:00</published> <updated>2026-03-04T02:37:49+00:00</updated> <id>https://lipeozyy.github.io/posts/APC-injection/</id> <content type="text/html" src="https://lipeozyy.github.io/posts/APC-injection/" /> <author> <name>Felipe</name> </author> <category term="Malware" /> <summary>⚠️ Disclaimer | Educational Purpose Only This content is provided strictly for educational and research purposes. All techniques, concepts, and examples discussed in this post are intended to support the study of information security, malware analysis, and defensive research in controlled and legal environments. The author does not encourage, support, or condone the use of this materi...</summary> </entry> </feed>
