Splintersfury

Malware analyst and cybersecurity professional focused on Windows kernel internals and reverse engineering.

[Splintersfury @Splintersfury]

Ihsan comes from the root word "Husn" (beauty). It means to do something so well that it becomes beautiful.

[Nicolas Krassas @Dinosn]

ThinkPad firmware reverse-engineering toolchain: archived Lenovo BIOS → named SoC pads, EC analysis, CVE diffs, coreboot/OpenCore port scaffolding https://t.co/diaaGki82i

[johnny @zeroxjf]

I forked Anthropic’s new vuln-discovery harness and made it Codex-first.

Recon → Find → Verify → Triage → Report → Patch

Sandboxed agents find bugs, prove them with crashing PoCs, dedupe, write exploitability reports, and validate patches.

https://t.co/0R8nhN2wbr

[KD @ChekhovianGun]

Jane Street guys are so incredibly cracked. Quite a few of their blogs are top tier and extremely intuitive. This one is a personal favorite of mine by @The_Numbat : https://t.co/XvHKsIfwlV

[𝕡𝕨𝕟𝕚𝕖 @0day_ninja]

ARM added Pointer Authentication as a hardware defense against ROP attacks. It cryptographically signs pointers using keys stored inside the CPU itself. Researchers defeated it using speculative execution. The CPU speculatively checks wrong signatures, rolls back before raising an exception, and leaks just enough to brute force the key. The hardware mitigation against speculation attacks was broken by a speculation attack.

Source: https://t.co/B40Y6U9SdX

[s1r1us (mohan) @S1r1u5_]

So @Doyensec recently published a report comparing @xbow and @AikidoSecurity, two AI pentest platforms.

I figured, why not run @HacktronAI on the same test? So I ran a pentest on one of the target. Hacktron cost $350, while XBOW and Aikido cost $4,000 each. We did pretty well!

[0xor0ne @0xor0ne]

Exploring the relationship between compilers, obfuscation, and de-obfuscation through LLVM, by Robert Yates (@quarkslab)

https://t.co/7rfwhEczcz

#infosec

[winterknife 🌻 @_winterknife_]

I was trying to hook some Windows driver dispatch routine and I got a BSOD which was weird because I could swear it worked before.
It appears that on Intel CET capable CPUs, you can't directly disable CR0.WP bit anymore.
Microsoft (prob) calls this mitigation WriteProtectGuard :)

[𝙿𝚜𝕪𐔖𝚙t𝐢ⅽ೦𝚗 @dubs3c]

@busf4ctor This applies to anything that can be statically defined. In general, only apply AI when the task is fuzzy and can’t be defined or codified. When the task is too big, break it up with temporary sub-agents (RLM), assuming reasoning is required. IMHO.

[Vitor Falcão "busfactor" @busf4ctor]

Here’s a hacking tip for using AI: whenever possible, make your process deterministic. If you need to scan JS files for postMessages, don’t just ask the AI to search for them. Instead, have it build an AST parser and run it on all the files.

Here’s an extra tip 👇

[Vansh Gupta @Vansh_95a]

"Yay! Today @hackerspider1 and I made $11,588 on @Hacker0x01 !"

#bughunters #bugbounty #hackers #hackerone

[Mr. Buzzoni @polydao]

the Atlassian engineer who was laid off dropped a full guide to becoming a senior engineer after 15 years in the industry

Vasilios Syrakis - no university degree. Made it to Senior Engineer anyway

the things that actually worked:

> taught himself Regex by mass-answering Stack Overflow until he became the expert people came to
> learned Python for free, immediately built a DNS web interface and shipped it - didn't wait to feel ready
> watched the same conference talks dozens of times until concepts actually stuck

if he was starting from zero today:

> get a CS degree - he skipped it and says that was a mistake
> build a home Kubernetes cluster and try to sell what you make
> grind LeetCode - not for the code, for the vocabulary to prompt Claude correctly
> share everything publicly - the audience compounds faster than the skills
> show up to meetups in person

the one mindset shift that separates juniors from seniors: when you join a new team, write a deep analysis of how everything works before touching a single line of code

> 15 years at the top of the industry and he still gets impostor syndrome

so does everyone else who's actually good

the roadmap is in the video 👇

[St0pp3r @_st0pp3r_]

Just published a new post in my Detection & Response Chronicles series.

This time I explore how adversaries abuse QEMU to run covert operations inside VMs, evading traditional host-based detection.

Read more: https://t.co/gkIubKGOwB

#QEMU #DetectionEngineering

[Andrew Dorman @AndrewCDormsn]

This was in response to my team giving them the root class 5 binary patch they used and the sh hardening for all 3 of @ChaoticEclipse0 zero days.
@msftsecresponse
Is now claiming ineligible under windows insider preview? Excuse me if I am dumb but wasn't @ChaoticEclipse0
Zeros all actively used in the wild?

I can see why he is doing what he is.......@MsftSecIntel
@msftsecurity
@Microsoft
Do fucking better.
Didn't even credit my team on UnDefend CVE while using the exact root laid forward. Let's go public about the whole chain if you like. I would love the public to run differentials on what I submitted and what you used and patched for both. You are screwing me like you did him. You are screwing my boy Damir who helped with all the work and made sure we gave you full engineering RE tracing to the fault lines.

Hi Andrew,

This case was recently re-assigned to me. After reviewing the history, I agree we could have handled communication more consistently, and I appreciate your patience.
Regarding your submission, as outlined in our public policy (see https://t.co/gCk3y8Ifv9.), publicly disclosed issues that are already known to Microsoft are generally not eligible for new case creation. Previously reported issues are treated as duplicates; while they may receive CVE acknowledgment, they do not qualify for bounty consideration.

We appreciate your effort and continued engagement, we look forward to receiving future submissions from you.

Best regards,
NV
Microsoft Security Response Center (MSRC)

[Mehmet INCE @mdisec]

Bro hacking Edge browser like it's a PHP 5.x app back in early 2000s. 🔥🔥🔥

[mufeed vh @mufeedvh]

another one! all of these are discovered with open models btw.

the blog will be published after all the findings are properly disclosed so we can talk about them in detail. there's a specific pattern to the kind of vulns these open models find, it's interesting!

https://t.co/Kz3PaFU5qW

[eversinc33 🤍🔪⋆｡˚ ⋆ @eversinc33]

Meanwhile me: "Claude, break this commercial protector with me" - "Sure!"

[Xint @xint_official]

Full technical deep dive available here: https://t.co/RsIMi8w4fb

[Suni @suni_code]

Found the Best Resource to learn Harness Engineering. 😭

https://t.co/3eOEmMlfbv

[Wils @zkWils]

After having spent years with the C programming language, I've decided to take it a step further like Zuhaitz, so I've decided to learn assembly

Wish me luck fellas 😶‍🌫️

[H4x0r.DZ 🇰🇵 @h4x0r_dz]

@ROCKY_HANDS0M the same one : "Audit the variable base scalar mul gadget for any missing constraints that
could lead to an inflation bug or double-spending attack against Zcash."
https://t.co/z0vOiJtMrQ