Sensors live. Logs retained.
Jacob Durham.
I reconstruct what happened. Then I publish it.
I publish as jacobrakai. Army veteran. Almost twenty years in networks, systems and security. I work from logs, artifacts and primary sources, and I write down what they prove and what they don't.
14,465,558
attacks recorded, all time
84,960
in the last 7 days
6,911
in the last 24 hours
12
investigations published in 2026
sensor data as of 2026-11-16 00:07 UTC · source: jacobrakai.org/feed
01
What the evidence shows
Questions I have answered from the record, in published work. The answer does not depend on what anyone remembers or says.
- Did the file run?
- Execution confirmed or ruled out from independent artifacts. registry · prefetch
- Did data leave the machine?
- Measured per application, after the fact. SRUM
- Who really sent the email?
- A compromised mailbox and a spoofed sender leave different traces. header forensics
- What did the browser do?
- A 40-second chain rebuilt after Incognito kept no history. SRUM · DNS logs
- Was the recording edited?
- A public meeting recording tested against the platform's own clock and thumbnails. storyboard · on-screen clock
- Does the citation say that?
- Statutes, court rules and forms checked against the primary source, with status and review date on a public table. primary sources
02
The record
Three of twelve. Each is a full write-up with evidence, limits and corrections.
Selected cases
092026-03Hunting through Chrome IncognitoThe browser kept no history. The operating system did.
122026-03Dissecting a ScreenConnect phishing attackThe dropper was quarantined and encoded. It was recovered anyway, and the logs showed no data left the machine.
012026-08 → 10RedTail brings its own key296 sessions, one key, three servers, ten weeks. All of it logged.
03
Rules
Written down, followed, and published next to the findings.
Always
- Primary evidence. Logs, artifacts and source documents.
- Stated limits. Every finding says what it does not prove.
- A name on it. Reports and submissions are made by a named person.
- Public corrections. Errors are fixed in place, with the original claim shown.
Never
- No offensive activity. Defensive work only, on infrastructure I own.
- No detonation. Samples are never executed.
- No guessing at people. A rented server identifies a box, not a person.
- No assertion past the evidence. What a record can't answer goes to a public-records request.
04
Identity
Everything here can be checked against a public record.
- name
- Jacob Durham, publishing as jacobrakai
- service
- United States Army veteran
- experience
- Almost twenty years in IT: networks, systems and security
- organization
- Jacobrakai Foundation, a 501(c)(3) public charity. EIN 33-3382083.
- orcid
- 0009-0001-6897-8860
- abuse reporting
- AbuseIPDB contributor
- memberships
- National Writers Union; Electronic Frontier Foundation, 2026
- contact
- Through the Foundation's contact details