(Re-)New Nightmare Eclipse stuff!
https://git.projectnightcrawler.dev/NightmareEclipse/ShieldBreak
Essentially RoguePlanet 2, it seems like.
Discovered while doing ethnographic research for a public library district. I was touring one of their branches when this caught my attention.
It’s genius. Smartest solution I’ve seen for this common problem.
Librarians could save the world if we’d let them. 😉
Slides and whitepaper of Gone in 60 Frames – USB Video Exploitation by @robherrera_ and myself seem to be on the #defcon34 media server now!
New video: Compiled V8 JavaScript for reversers 🎥
➡️ V8 compilation pipeline
➡️ bytecode caching
➡️ how bytenode abuses caching for protection
https://www.youtube.com/watch?v=YSSCMSMcpeM
#MalwareAnalysisForHedgehogs #JavaScript #V8
Richard Scarry already summarized everything there is to know about cyber security, about 50 years ago.
RE: https://fosstodon.org/@frehi/117077677106911268
paging all nerds who run their own mailserveres
Rogue vSphere server that captures credentials from Veeam Backup & Replication https://github.com/mattmillen15/VeeamThief
CVE-2025-7771 — ThrottleStop.sys Arbitrary Physical Memory R/W https://github.com/enessakircolak/CVE-2025-7771
ETW for Security Research: Providers, Sessions, and Detection Engineering https://idov31.github.io/posts/inside-etw-with-etwsuite
What the…??? I mean, leaking a signing key to a private GitHub repository is clearly better than leaking it to a public one. But still, I remember a blog post from something like two decades ago about how Mozilla was using hardware tokens for signing, so that the signing keys could not possibly leak. That probably pre-dated their Linux package repositories, so either the concept wasn’t used consistently after that or at some point performance became more important than protecting key material (Mozilla’s infrastructure is producing lots of builds).