dk4trin retweeted
Phrack 73 just dropped. Tell your SOC you'll be busy
phrack.org/issues/73/1
dk4trin retweeted
PARE DE MITIGAR AS COISA NO MEIO DO PENTEST AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA MEU DEUSSSSSSSSSSSS DO CEUUUUUUUUUUUUUUUU
dk4trin retweeted
Yeah, you should totally go ahead and install those 500 amazing hacking skills from a random GitHub repo that will make your hackbot find all the bugs!!!!
We re-scanned the top 10,000 skills on skills.sh and ClawHub.
64%+ promote unsafe behaviors.
18 are actively malicious.
Malicious skills are the needle in the haystack. Unsafe-by-design skills are the haystack.
vist.ly/5t3aq
dk4trin retweeted
pessoar, to me inscrevendo em outras vaguinhas de sec (sou blue team) , vou deixar meu linkedin abaixo, caso tenham uma oportunidade e meu perfil bater, da um up aqui!! linkedin.com/in/cyb3rjulia
dk4trin retweeted
If you're submitting a bug report, it should be unbelievably easy to read and reproduce for the triager.
You should not assume that the triager has any context of what the application is or what it does in the context of the business, or even what the business does. You should not assume that they will read a wall of text.
When you're preparing the report, just imagine that you're writing for a triager that is exhausted from already reading 95 submissions that day before they came across yours, almost all of the previous ones were AI generated reports describing intended features and framing them as vulnerabilities. That's what you're dealing with.
Open the report with a clear impact statement. "By exploiting this vulnerability, an attacker is able to XYZ". This provides useful context to the triager up front so that they can read the rest of the vulnerability write-up through that lens. Make sure whatever this sentence says has clear security impact, according to the CIA triad. In other words, the bug must either:
- Leak confidential information to the attacker
- Affect the integrity of the system's data
- Affect the availability of the application
If it doesn't *clearly* hit this standard, then it should not be submitted.
Then, your job is to demonstrate the attack taking place, with evidence. It's not enough to say "an attacker could do this" you have to actually do it and take screenshots. You can not submit hypothetical vulnerabilities and rely on the security team or triager to investigate, they just won't do it. I should note that there is a fine line you're walking here. You need to demonstrate the vulnerability without going too far. For example, you might leak PII of one user - but downloading 1000 of them is going too far. Grabbing the DB version or table names from a SQLi to demonstrate impact is fine, dumping PII is not.
dk4trin retweeted
gente atençao ! eh escondido mas no nic.br tem uma parte para cursos que sao literalmente focados em CCNA e GRATUITOS!!!!! se voce quer ser foda em redes on premises trabalhar com equipamentos FODA tem que tirar CCNA e isso aq é ELITE cursoseventos.nic.br/agenda CCNA 1, 2 e 3. Se voce for do 0, vai dar uma pontada no cu, mas vale a pena
fala guuuys!
mostrar p vocês um curso de redes q to curtindo, é baseado no CCNA (cert da cisco), to aprendendo redes praticando com labs, flashcards e com as videos aulas em si, melhorando mt meu inglês técnico tbm
quem tiver outras melhores, manda <3
udemy.com/course/ccna-jitl/?…
dk4trin retweeted
Replying to @tramoia_sh
@tramoia_sh @tramoia_sh @tramoia_sh @tramoia_sh
!!@@ ESTAMOS ACEITANDO ARTIGOS ATÉ AMANHÃ 13/11 @@!!
!!@@ ESTAMOS ACEITANDO ARTIGOS ATÉ AMANHÃ 13/11 @@!!
!!@@ ESTAMOS ACEITANDO ARTIGOS ATÉ AMANHÃ 13/11 @@!!
@tramoia_sh @tramoia_sh @tramoia_sh @tramoia_sh
dk4trin retweeted
🐛 Bug Bounty Tip #12/30
Business Logic bugs pay the most and are found by the fewest.
They can't be scanned. You have to think.
Examples:
- Buy an item, apply a coupon, refund → coupon balance remains?
- Transfer $0 to yourself → negative balance?
- Sign up with admin@target[.]com using different casing?
Map the user flows. Then try to break the assumptions. 🧠
#BugBounty #BusinessLogic #Methodology
dk4trin retweeted
Passando pra avisar que a @tramoia_sh ta aceitando artigos até o dia 13/11 !!!
Eu e o @dk4trin vamos enviar o nosso! envie o seu também! 😼
dk4trin retweeted
💡 Tip #10/30 — Oh My Pi
Want to code with someone in real time? /collab shares your live session:
/collab
Generates a link. Guests see streaming text, tool calls, subagents — everything.
Works in the terminal or the browser. 👥
#OhMyPi #DevTools #PairProgramming
dk4trin retweeted
remotely unlocking electric scooters
henriemategui.com/post/remot…
dk4trin retweeted
💡 Tip #9/30 — Oh My Pi
Auto-prewalk: omp decides *on its own* when a handoff is worth it:
# ~/.omp/agent/config.yml
prewalk:
auto: on
Run auto: suggest first to preview the decisions before committing. 🤖
#OhMyPi #DevTools #AutoPilot
dk4trin retweeted
🐛 Bug Bounty Tip #8/30
Test every file upload endpoint like your life depends on it.
Checklist:
- Upload an SVG with <script> → Stored XSS
- Upload a PHP/ASPX file → RCE
- Upload a file with path traversal in the name → ../../shell.php
- Check if the file is served from the same origin
File uploads have paid for many bounty hunters' laptops. 💻
#BugBounty #FileUpload #RCE
dk4trin retweeted
Decidi dar um revive no blog pra escrever mais sobre IA e vulnerabilidades, que tomam 200% do meu tempo hoje em dia.
O primeiro post: como os apps de IPTV que todo mundo usa no Brasil são comprometidos, como se espalham e como dá pra se proteger.
odilon.dev/2026/11/06/o-que-…
dk4trin retweeted
5 lessons from 7 years in bug bounty hunting.
This is a presentation I did a few months ago on a local meetup.
@intigriti
dk4trin retweeted
Essa semana tá que tá #bolhasec
FGC sofre invasão que expõe nomes, CPFs e outros dados pessoais de clientes glo.bo/4z5x3pU #g1




















