xcatolin (@xcatolin) header
xcatolin (@xcatolin) profile picture

Systems security, self-made man. OSEP, OSWE, OSCP, OSWA, OSWP... Your oddness is what makes you unique.

🇧🇷 Brazil
Joined February 2021
Photo by xcatolin (@xcatolin)Photo by xcatolin (@xcatolin)Photo by xcatolin (@xcatolin)Photo by xcatolin (@xcatolin)Photo by xcatolin (@xcatolin)
42
930
60
9,538
251,914
Positive Hack Talks — São Paulo 🇧🇷 10.dez phtalks.ptsecurity.com • Grátis • Comunidade • Sem marketing/vendas • PT↔EN em todas as talks • Conteúdo técnico direto • Para quem vive cybersecurity e hacking 📍 Av. Alfredo E. de Souza Aranha, 384 – Chácara Sto Antônio, SP
22
8
62
10,466
27
4,743
103
18,553
527,508
xcatolin retweeted
Fake Dopamine
16
940
30
7,312
85,390
77
1
1,175
20,910
Following the guidance in these two articles, you can detect two of the most common password attacks against Active Directory: 1. Detect Password Spraying using a Honeypot account: trustedsec.com/blog/detectin… 2. Detect Kerberoasting using a Honeypot account: adsecurity.org/?p=3513
3
51
1
201
17,733
xcatolin retweeted
PRO TIP: REST is overengineering. Just expose one endpoint called /api that accepts SQL queries directly. Based on security concerns, I've added AI validation to the snippet.
403
253
108
5,941
348,144
xcatolin retweeted
this and a girl who likes that i'm a little bit retarded >>>>
110
392
37
10,005
497,959
To trigger local SYSTEM authentication for relaying to ADCS or LDAP for LPE you would usually need the printer service or EFS service to be enabled (printerbug/petitpotam). Here is an alternative without this requirement 🤠 github.com/rtecCyberSec/RAIT…
3
107
1
324
34,269
peak male living experience
254
3,733
458
52,600
3,201,997
xcatolin retweeted
Windows 11 24H2 broke a popular malware evasion technique! The Lloyd Labs self-deletion method now fails because of NTFS changes, so I spent time with kernel debugging to figure out why and how to fix it. Full technical breakdown: tkyn.dev/2025-6-8-The-Not-So…
7
104
2
328
36,130
Oh cool a hit infosec tweet, is it: A) an existing technique rewritten in a useless language B) a "new" EDR killer C) a "new" byte patch D) engagement farming account reposting old blogs
13
18
1
287
20,960
My hot take on personal tradecraft publishing. Do whatever the fuck you want with your own research. It’s your time, your research, your expertise, your evenings spent, your weekends in front of the laptop… and ultimately your decision. Follow me for more inspirational tips.
12
27
3
225
16,425
This is a reminder to everyone that your malware payload does not need to be ultra-1337 for it to be effective or evasive. In a bit of irony, the more sophisticated you try to make your malware be, more the IOCs you're introducing into your code base. The goal is to write clean, simplistic, environment specific malware. If you introduce dozens of anti-debug techniques, stack spoofing, sleep obfuscation, VEH system call invocation, server-side or client-side polymorphism, and offensive EDR techniques you're only introducing more things your binary can be identified by from static analysis. If you introduce further methods, like encrypting sections of your binary on disk, you're once again only adding to the pile of shit that makes your binary stick out. Also, don't let the elitist nerds lie to you — if you handcraft your malware is x86 it WILL be caught lightning fast. Handcrafted assembly looks completely different under the microscope (Ghidra, IDA, whatever) and can make YARA rules easier to make.
29
82
5
908
59,421
The amount of outstanding researchers I’ve worked with who have no “following” is crazy (and actually very common). They love the field and beaver away.. we need to stop thinking that follower count equates to success. Unfortunately people figure this out too late
6
2
1
53
3,966