Phrack 73 ships with 23 main papers and eight Line Noise pieces

Phrack Staff has published the introduction to a new issue of the long-running hacker zine, dated September 30, 2026. It is the third release curated by the new staff, and the staff says it is not slowing down. The issue is larger than last year's, with 23 main papers and eight additional articles in the Line Noise section. Subjects range from exploitation and reverse engineering to machine learning, hardware, and the history and culture that grew around this work.

The introduction lists the technical topics. They include container escapes through the vDSO, use-after-free exploitation, QNX userland shellcode, Linux kernel research, and a Chromium renderer sandbox escape through Skia. The issue also covers Windows smart card architecture, static taint analysis in Binary Ninja, and autonomous underwater vehicles. There is work on backdoors in machine learning and on what it means to trust an AI system. One paper goes from PhrackCTF to two WinFSP zero-days, which the staff calls a pretty good argument for continuing to put challenges in a zine.

The history section, Phrack World History, has four more articles. One tells the story of the infamous SSH1 CRC32 vulnerability, which the staff says was featured in The Matrix Reloaded. Others cover blue boxing for free phone calls, a confession from a hacker who tried to backdoor the Linux kernel in 2003, and an early discovery of botnets for hire. The Prophile features Halvar Flake, whose contributions to reverse engineering and security research the staff calls legendary.

Looking back, the staff notes that last year was Phrack's 40th anniversary, so it went big. The anniversary launch release came out in print at Defcon 33, HOPE and WHY25, with additional variations at conferences including AlligatorCon, B-Sides Canberra, Out of the Box, Datenspuren, DistrictCon, OffensiveCon, Recon and Toorcamp. It had a CTF with exploit challenges, puzzles and easter eggs in the zine, plus parties and talks at Defcon and WHY25. The stated goal of the relaunch was to get people reading, researching, writing and contributing again, so that the next person picking up Phrack would find something that made them sit down at a computer and start pulling a system apart.

On the future, the staff writes that in 2026 it is hard to say what vulnerability research or red teaming will look like in another five years. In its words, AI has moved well beyond completing a line of code into agentic systems capable of analyzing source code and reverse engineering binaries to find and exploit vulnerabilities. It argues that as the effort needed to put ideas into practice falls, creativity and human intuition forged through experience are valued even higher, and it hopes the release keeps the human side of hacking a critical element in shaping technology and society. It closes with a call to read the papers, try the ideas, challenge the conclusions, and send in a write-up when you find something worth sharing.

The credits thank authors, editors, artists, publishing partners, donors and staff. Conferences that funded the print editions are named: Defcon, OffensiveCon, Recon, Unprompted[AU], Unprompted[US], BSides Canberra, Alligatorcon and TenguCon. Sponsors and major donors include WatchTowr, Elltam, Verichains, BShield, TrustedSec, Binarly, Trenchant, Praetorian, EFF, Blaze, EMX, Mullvad, ToorCon and Hacker Initiative, among others.

Key facts

  • The new Phrack issue carries 23 main papers and eight additional Line Noise articles, larger than last year's, and is the third release curated by the new staff.
  • Topics include container escapes through the vDSO, use-after-free exploitation, QNX userland shellcode, a Chromium renderer sandbox escape through Skia, Binary Ninja taint analysis, and a PhrackCTF-to-WinFSP path that ended in two zero-days.
  • Phrack World History adds four articles: the SSH1 CRC32 vulnerability, blue boxing, a hacker's confession about trying to backdoor the Linux kernel in 2003, and early botnets for hire. The Prophile features Halvar Flake.
  • The staff says AI has moved beyond line completion into agentic systems that can analyze source code and reverse engineer binaries to find and exploit vulnerabilities, and argues human creativity and intuition become more valuable.
  • Last year's 40th anniversary release was printed at Defcon 33, HOPE, WHY25 and several other conferences, which funded the print editions.

Why it matters

Phrack is a 40-year-old hacker zine, and its staff says the relaunch aims to get people reading, researching, writing and contributing again. This issue is the follow-through: bigger than last year's, with 23 main papers and eight Line Noise articles. The introduction also gives the staff's view of where the field is heading. It says AI has gone from completing a line of code to agentic systems that can analyze source code and reverse engineer binaries to find and exploit vulnerabilities, and that it is hard to say what vulnerability research or red teaming will look like in five years.

Who it affects

The issue is aimed at vulnerability researchers, reverse engineers, red teamers and hackers more broadly. Topics touch Linux and container security, Windows (smart cards, WinFSP), Chromium and Skia, QNX, hardware, and machine learning, including backdoors and trust in AI systems. The history section and the Halvar Flake Prophile also speak to readers interested in the culture around the field.

How to use it

The staff's own instruction is to read the papers, try the ideas, and challenge the conclusions. When you find something worth sharing, write it up and send it in; the introduction lists submissions[at]phrack{dot}org for that, and says ANTISPAM must go in the subject. The staff notes that one paper's path from PhrackCTF to two WinFSP zero-days shows the value of putting challenges in a zine.

How solid is it

This is the editors' own introduction to the issue, so it is a description of the contents rather than an assessment of them. It names topics and does not give technical findings. The issue number 73 appears in the page address and title, not in the introduction text. The staff's remarks on AI are its own view and come without supporting data. Phrack's disclaimer says that, to the best of the editors' and contributors' ability, all facts are checked and all code is compiled, but that something in the publication may still be incorrect.

Risks and caveats

The introduction lists topics only; the vDSO escape, the Skia sandbox escape and the WinFSP zero-days are not described in detail. It does not say whether the WinFSP zero-days were patched. Phrack's disclaimer says it accepts no responsibility for the stupid or illegal things people may do with the information, and that the opinions in articles belong to their authors and do not necessarily represent those of the Phrack Staff.

“The point of the relaunch was to get people reading, researching, writing, and contributing again.”

— Phrack Staff, introduction to the issue