<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://pr1n5.github.io/</id><title>pr1n5's blog</title><subtitle>I like breaking stuff</subtitle> <updated>2026-06-29T19:36:10+00:00</updated> <author> <name>pr1n5</name> <uri>https://pr1n5.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://pr1n5.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://pr1n5.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 pr1n5 </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Exploring the Offensive Potential of the Windows Cloud Files API</title><link href="https://pr1n5.github.io/posts/Cfapi-Cloud-Files/" rel="alternate" type="text/html" title="Exploring the Offensive Potential of the Windows Cloud Files API" /><published>2026-06-26T00:00:00+00:00</published> <updated>2026-06-29T19:35:54+00:00</updated> <id>https://pr1n5.github.io/posts/Cfapi-Cloud-Files/</id> <content type="text/html" src="https://pr1n5.github.io/posts/Cfapi-Cloud-Files/" /> <author> <name>pr1n5</name> </author> <category term="Evasion" /> <summary>A couple of weeks ago, I started messing around with some of the techniques used by the LPE BlueHammer, specifically the Cloud Files-related parts. While my goal isn’t to recreate the exploit (mainly because it relies on several other techniques, and reimplementing it from scratch feels completely insane), I was particularly intrigued by everything surrounding the Cloud Files API. I had no idea...</summary> </entry> <entry><title>It's me, Pipe. Don't mind me.</title><link href="https://pr1n5.github.io/posts/Named-pipes-nightmare/" rel="alternate" type="text/html" title="It&amp;apos;s me, Pipe. Don&amp;apos;t mind me." /><published>2026-06-07T00:00:00+00:00</published> <updated>2026-06-08T10:22:08+00:00</updated> <id>https://pr1n5.github.io/posts/Named-pipes-nightmare/</id> <content type="text/html" src="https://pr1n5.github.io/posts/Named-pipes-nightmare/" /> <author> <name>pr1n5</name> </author> <category term="Persistence" /> <summary>Over the last couple of weeks, I’ve been messing around with one of the Windows API features that had been sitting on my to-do list for a while, Named Pipes. If you don’t know what they are, they’re basically channels that processes use to exchange information. They work through a file-like interface (kind of like Linux FIFOs) and, best of all, they can even be used to communicate with remote p...</summary> </entry> <entry><title>Persistence with kernel modules</title><link href="https://pr1n5.github.io/posts/persistance-with-kernel-modules/" rel="alternate" type="text/html" title="Persistence with kernel modules" /><published>2025-05-10T00:00:00+00:00</published> <updated>2026-06-08T10:22:08+00:00</updated> <id>https://pr1n5.github.io/posts/persistance-with-kernel-modules/</id> <content type="text/html" src="https://pr1n5.github.io/posts/persistance-with-kernel-modules/" /> <author> <name>pr1n5</name> </author> <category term="Malware" /> <summary>In this post, I’m going to explain the idea behind this module, its applications, and some interesting things I discovered while working on it. Then, I’ll show you a PoC of this file, followed by some additional considerations and some few upgrades I think could be interesting to implement. Before things went downhill Chronologically, this module is the first piece of “malware” I’ve created —...</summary> </entry> <entry><title>RATs Over My Wire</title><link href="https://pr1n5.github.io/posts/rats-over-my-wire/" rel="alternate" type="text/html" title="RATs Over My Wire" /><published>2025-04-20T00:00:00+00:00</published> <updated>2025-04-21T14:42:53+00:00</updated> <id>https://pr1n5.github.io/posts/rats-over-my-wire/</id> <content type="text/html" src="https://pr1n5.github.io/posts/rats-over-my-wire/" /> <author> <name>pr1n5</name> </author> <category term="Malware" /> <summary>In this post, I’m gonna walk you through how I built my own custom RAT (Remote Access Trojan). I’ll show you how many detections it got on VirusTotal, and give you a quick PoC so you can see it in action. After checking out the code, I’ll also throw in a few ideas on how to tweak it to dodge more defenses. Initial Thoguhts and Goals First of all, let’s define a RAT as a Remote Access Trojan. ...</summary> </entry> </feed>
