
The lyf so short, the craft so long to lerne. - Chaucer

vx | systems | networks | security | prof @uc3m

The lyf so short, the craft so long to lerne. - Chaucer


It’s great (in a not-so-great way) to see a brand-new polymorphic Windows file infector and USB worm built in 2026.
New file infector in 2026? Does anyone know what this is? It looks like some toy that got out of hand. Currently flooding us via VT and other sandboxes, they are all constantly generating new copies of it... research.openanalysis.net/hd…

Nov. 18, 2026, 5:16am EST The Voyager 1 spacecraft has reached a distance of one light-day from Earth.

For better or for worse, Barlow's Declaration of the Independence of Cyberspace has not aged well.
Quad9's forced withdrawal from France highlights the dangers of mandating DNS-level blocking. Read more: cfl.re/4f0cowv

Had the privilege of giving a talk at my second init.g(Málaga) last weekend. It is an amazing event, and it was truly great catching up with longtime colleagues (thank you @gerardofn!) and meeting new ones. Slides are up. More details soon! 0xjet.github.io/talks/2026_i…

Phrack 73 just dropped. Tell your SOC you'll be busy phrack.org/issues/73/1

I am sharing a new paper today with Dario Caldara: “Can Peer Review Survive AI-Generated Text?” sas.upenn.edu/~jesusfv/Peer_… Dario and I, as editors, are increasingly getting papers submitted to our journals that are 99 percent AI-generated. Even worse, we are also receiving many AI-generated referee reports, both as editors and, more frustratingly, as authors. And we cannot emphasize this enough: the real problem is not that the papers and reports were AI-generated; it is that no one had done the thinking behind them, and you can so easily tell. The papers were eminently forgettable, and the referee reports were disappointingly uninsightful. We have seen too many reports of the form: “The paper is well-written and addresses an important problem. However, the authors should consider additional baselines.” This deluge of AI-generated text puts peer review in jeopardy: journals will be flooded with low-quality submissions, economists will decline requests to referee papers or routinely use AI to referee them, and which papers get published will become less and less linked to their quality. We do not want to defend the status quo entirely. Peer review is slow, many reports are poor, and editors (including us!) make bad calls all the time. Still, well-executed peer review remains the best system we have for assessing each other’s work and advancing the profession. AI could improve peer review if used deliberately for that purpose, for instance, to check proofs and code. That is not what we are seeing. The difficulty is that readers, including editors and referees, cannot see how AI was used. As a result, in practice, the burden of verification shifts from the author to the reader. Since we reject this shift, Dario and I did what economists always do when something bothers us: we wrote a paper. So, what do we do in it? First, we check whether AI detectors such as Pangram get this right: is a referee report flagged as AI-generated indeed AI-generated? Or is Pangram just flagging proofreading and editing? No. We run an experiment with 25 referee reports from the pre-AI era. Proofreading and editing do not trigger AI-generated flags. Only when we ask the LLMs to substantially rewrite the referee report or to generate a new report do we get the AI-generated flags. Pretty compelling evidence, if I may say so. Second, we build a theoretical model to explore who should bear the burden of verification: the author or the reader? (Yours truly always enjoyed the courses on the rules of evidence in law school; yes, as Billy Wilder would say, nobody is perfect.) The answer is that it is much more efficient for the author to do it, because the author can verify at a much lower cost and only needs to do it once (rather than each reader repeatedly). Before AI, the authors more or less had to verify the results, even if only because they had to type them in. This was not perfect (and all papers ever published in economics probably have at least one mistake). But the problem is that, with AI, the author does not even need to read the text. Or can just skim it. Writing is thinking, and without writing there is usually not much thinking. So, a paper flagged as AI-generated is prima facie evidence that the author has not verified it. Should this lead to an automatic rejection? No. But there should be a zero-tolerance policy for serious mistakes. The first serious mistake we find in the paper, and it is out! In comparison, for a non-flagged paper, a serious mistake is something that the editor might determine it can be fixed in a revision. We are stricter with referee reports. There is absolutely no point in the referee generating a report using an LLM. As an editor, I can do that directly and save myself the trouble of asking you for it. Now, of course, you can use the LLM to help you with the report (if the journal allows it! Many journals do not allow you to upload the paper to an LLM, and you need to follow the rules). For example, you can use the LLM to search for existing results in the literature. But peer review is not about finding one sentence that is not entirely precise or a slightly sloppy mathematical proof. Referees are asked: “Is this idea important despite its flaws?” And, relatedly: “Is the paper a good fit for the journal in terms of quality and focus?” That judgment is the task for which you are selected as a subject expert. We also propose that journals require that, before a paper is submitted, the author submit it to an LLM using an approved prompt and include the LLM report and a discussion of what was and was not fixed. That way, the referee would not need to check (or at least not check so carefully) every technical detail, and they could focus on the big picture: Is this a good paper? Is this a good fit for this journal? What is fundamental for this paper to become publishable at this journal? Anyway. The paper has many other arguments, and we try to be nuanced. So, before ferociously typing the first complaint that crosses your mind, would you consider reading it? Chances are that we have already discussed your objection. We have been thinking about this for a long time. But by all means, leave good comments!

My team at Apple SEAR has an internship opening in cellular baseband security research! Apply here: jobs.apple.com/en-us/details… If you're a Master's/PhD student who enjoys reverse engineering baseband firmware, building emulators, and finding vulnerabilities in cellular stacks and protocols, we'd love to hear from you. Feel free to reach out with any questions. #cybersecurity

Researchers(Mark Ermolov, Dmitry Sklyarov, and Maxim Goryachy (from Positive Technologies)) found two undocumented x86 instructions, udbgrd and udbgwr, that can read and write microarchitectural data directly. They enable access to the microcode patch RAM and match-and-patch structures inside the CPU. UDBGWR is capable of modifying MSRAM and updating match-and-patch entries that override target instructions. Intel has never documented these instructions but they're callable from user space and they give direct write access to the CPU's microcode storage.

i can count on zero hands the number of times ive wanted something displayed as signed hexadecimal

The USCSS Nostromo’s supercomputer “Mother”, from Ridley Scott’s “Alien” (1979)

VirusTotal is now available in Claude claude.ai/directory/virustot…

I am kicking off my CTI course today with a quote one of my kids gave me last year.

Hudson Rock: infostealer logs are now sold as AI-written machine profiles you can search in plain English. A clinic front-desk PC with Citrix access went for $10. infostealers.com/article/ins…