.:: PHRACK NEWS ::.

–[ Phrack 73 Call For Papers

Why should you write for Phrack?

- You have a project you've been working on that pushes the limits in some 
  way, doing things that haven't been publicly shared before. If you do 
  cutting edge security research, you should write for Phrack.

- You are interested in aspects of security and technology that other people
  don't seem to care about or understand. If you feel like you need to shed
  light on a certain topic for all to see, you should write for Phrack.

- You keep seeing the same problems over and over and wish someone would 
  just write a straightforward guide for everyone. If you are the person 
  who can write that for now and future generations, you should write for 
  Phrack.

- You deserve a place to share your finest work without fear. If you don't
  want something you poured your heart and soul into turned into another 
  metric for shareholders and potential investors or trapped forever inside
  a corporate VPN, you should write for Phrack.

Worst Case Scenario: You just wrote a cool paper you can share on your own.

Best Case Scenario: Your paper gets published in Phrack. :)


::. What do we want? .::

Articles about hacking, exploit development, vulnerability research, and 
other fine topics.

More Specifically:  

- Exploitation: Demonstrate the latest techniques in breaking mitigations 
  and proving vulnerabilities still have bite.

- Persistence: Whether its userland, kernel, or below ring0, share a trick 
  in the dark art of stealth persistence.

- Fuzzing and Code Analysis: Automated bug hunting finds the low hanging 
  fruit, how can we make it more lethal?

- Binary Obfuscation: We have decompilers but custom VMs and powerful 
  transformations create impenetrable code.

- Data Obfuscation: Time to exfil, how do you move a terabyte of data 
  without looking like a fool?

- Anti-Forensics: Leave no trace, hide in the mist, or maybe even deploy 
  countermeasures on the parsers!

- Web Applications: Discuss confusion, bypass, and injection attacks on 
  the multi-headed hydra of modern applications.

- Cloud Security: Complexity and lack of visibility is the soft underbelly
  of cloud compute, discuss.

- Data Storage Weaknesses: If data theft is the end goal, let's talk about 
  all the leaks in storage infra and APIs. 

- Exploit Mitigation: Finding every bug is futile, how do we design more 
  secure systems to block these attacks?

- Malware Analysis: The world is covered in a diaspora of malware, flay 
  open the code and inspect the innards.

- Malware Defense: We wade in a pool of parasites attacking from every 
  angle, how do we block their vicious effects?

- Exotic Reverse Engineering: What are the corrupt hidden hands of power 
  in this electronic substrate?

- Scene History: Let us learn the often isolated tribal history that hasn't
  been written about before.

- Tales from the Crypt: Want to tell a personal story of a righteous hack?
  Maybe we'll believe you.


::. When Do We Want It By? .::

June 2026



::. When will Phrack 73 be released? .::

Summer 2026

                   ----( Contact )----

    <  Editors           : staff[at]phrack{dot}org         >
    >  Submissions       : submissions[at]phrack{dot}org   <
    <  /dev/urandom      : loopback[at]phrack{dot}org      >
    >  Arts & Leisure    : arts[at]phrack{dot}org          <
    <  Twitter/X         : phrack                          >
    >  Mastodon          : phrack[at]haunted{dot}computer  <
    <  BlueSky           : phrack{dot}org                  >


    The rules are simple:

    + 7-bit ASCII wrapped to 76 columns OR Markdown UTF-8
    + ANTISPAM in the subject line or face the Spam God and 
      walk backwards into hell