prxcess monitor retweeted
The researchers are Daniel Trujillo and Mengjia Yan share.google/QjeqBOnZIne9yKO…
MIT researchers found a CPU side-channel called Interrupt Injection that cuts straight through Spectre v2 defenses on both AMD and Intel chips.
By arranging a hardware interrupt to arrive precisely at the right moment, unprivileged user-space code can re-poison the branch predictor after the defense has executed but before the CPU relies on the prediction.
The timing window exists in the gap between OS implementation and CPU protection. You can pull Linux password hashes from kernel memory despite modern mitigations.
prxcess monitor retweeted
I've been using ARTEX, and recorded a deep dive solo podcast about it, CAIRN, and AntiFox. There's a lot to learn about harness design and turning offensive tools into defensive machinery. Hour long. Link below!
prxcess monitor retweeted
Finding Zero-Days with Any Model - @nielsprovos
Vulnerability discovery is an orchestration problem, not a frontier-model problem.
provos.org/p/finding-zero-da…
prxcess monitor retweeted
New lecture on pwncollege, presented by guest lecturer Jennifer Miller (Zolutal) from the SEPCOM lab, provides an introduction to Linux kernel security and exploitation concepts within the context of the CSE466 course (0:00-0:15).
Key takeaways from the lecture:
> Kernel Basics: The kernel acts as the interface between hardware and userland applications, handling task scheduling and interprocess communication (1:08-1:36).
> Kernel Modules: These are extensions to the kernel, ranging from drivers to security modules. They can be in-tree (part of the kernel source) or out-of-tree (proprietary/external) (2:46-3:51).
Interacting with Modules: The lecture demonstrates how modules expose functionality to user space, specifically through `/proc` entries and the `ioctl` system call (3:51-6:07).
Exploitation Concepts:
> Privilege Escalation: A primary goal, often involving the manipulation of the `task_struct` and `cred` structures to set the effective UID to 0 (root) (11:03-13:09).
> Memory Protections: Discusses mitigations like KASLR (Kernel Address Space Layout Randomization), which randomizes memory positions (15:08-16:00).
> Kernel Shellcoding: Unlike user space, kernel shellcode calls internal kernel functions directly. The lecture demonstrates allocating RWX (Read-Write-Execute) memory pages and triggering execution through a modified kernel module (8:51-11:03, 42:00-58:50).
> Debugging: The lecture provides practical guidance on using GDB to interact with the guest kernel, noting the challenges of debugging with hardware-assisted virtualization and the benefits of using emulator mode (7:55-8:41, 51:42-55:17).
youtu.be/8gAZuA67QA8
prxcess monitor retweeted
Getting bored over the x-mas holidays ? Your AI friend is bored too ? Not any more ....
github.com/bkerler/exploit_m…
Added 6 more vulnerabilities, 35 now in total !
prxcess monitor retweeted
stop bug hunting modal AI tanpa ngerti bugnya samsek, hunting cuma modal hermes sama model cina trs rapihin laporannya biar gak keliatan slop, padahal temuan bugnya sendiri aja udh jelas2 slop, no impact + hasil halu AI yg endingnya malah akan ngerusak ekosistem bug bounty 😹
bug bounty ini ternyata banyak capeknya
maintenance agent dlu, setup skill, agent md soul md dan ngeluarin token banyak dan berakhir dengan duplikat
untungnya gw jalanin agent gw tanpa ngeluarin duit pribadi apapun itu, itulah mengapa awal gw pelajari itu gimana caranya crime agent supaya gw bisa stock dari opsi gratisan
dan yaa gak semua orang yang bisa membuat agentnya crime, dan gak semua orang yang mau ngasih metodenya
indahnya gatekeep
prxcess monitor retweeted
> PS5 jailbreak team just figured out the GPS for their exploit
> a table inside the browser called GOT.PLT
Yeah we teach this to 15-year-olds as intro to pwning at Cyberchallenge bro 😭 goddamn we are cooked…
- Paket data mahal
- Sinyal jelek
- Udah di-backdoor sama "jaksa muda intel"
Si "jaksa muda intel" inilah yg nulis buku penyadapan dan juga doxing akun yg menyebut Señor D
1
4
166
How to rebuild a sharp brain:
1. Read physical books (no e-books)
2. Watch long, boring movies or documentaries
3. Journal and write by hand
4. Practice math using school textbooks ( my personal fav)
5. Go on walks with zero music/podcasts
6. Summarize what you just read from memory by writing it
Boring habits heal a fried attention span, trust me
prxcess monitor retweeted
Working on linux a lot these days during my spare time, and can't stress enough on how good this read is.
If you want to understand the details behind the memory allocation, please go -
sourceware.org/glibc/wiki/Ma…
prxcess monitor retweeted
Yang nanya kapan liputan investigasi @hariankompas soal judi online... Kita udah melakukan investigasi judol hampir tiga tahun lalu gaes. Makanya kita tahu banyak siapa para pemainnya.
Nih gw spil salah satu hasil investigasinya. Tiga tahun lalu ini...
kompas.id/artikel/judi-onlin…
The Commission (New York) ❌️❌️
The Sicilian Commission ❌️❌️
The Indonesian Commission ✅️✅️🤑🤑
Dulu di FGD gua pernah bilang justru koruptor ga akan kena.
Mereka udah layering aset
Mereka ada lawyer mahal sesuai bidang mulai dari tax lawyer sampe yg spesialis belokin pasal.
Gua di cut dari fgd itu 🤣🤣🤣
1
213
prxcess monitor retweeted
5 agentic offensive frameworks skip in-code authorization by default.
ARTEX, CyberStrikeAI, Cairn, PentAGI, and HexStrike put an LLM in the planning loop around familiar scanners, shells, and cloud CLIs, and GTIG observed ARTEX acting in bursts of roughly 2 to 25 seconds.
All 5 have already turned up in real intrusions, across reporting from GTIG, Mandiant, Microsoft, and our own research.
We read their source and the public incident reporting to work out what reaches defender telemetry. Research by @stryker0x: go.es.io/4eKv4jE
• Why IOC and User-Agent detections go stale while behavior-based rules hold up
• Tempo and sequence signals per identity for short bursts and long campaigns
• An ES|QL hunt for tool-family bursts across web, proxy, and cloud audit logs
• Why blocking a source IP must be paired with credential/session revocation
Every action these frameworks take still has to land in telemetry you already collect.






























