From HFT to Infosec: How AI Accelerates the Developer-Hacker Arms Race

An experienced security researcher draws a parallel between high-frequency trading evolution and modern vulnerability research, showing how artificial intelligence compresses the time between patch release and working exploit. The author describes the classic workflow where developer Rob fixes buffer overflows in an FTP server while researcher Dave reverse-engineers the diff to locate the exact change. With AI assistance, both sides now generate patches or exploits in minutes rather than days or weeks. The piece highlights that publishing a patch effectively discloses the location of the flaw, allowing automated tools to produce reliable exploits almost instantly. Historical examples such as wu-ftpd CVEs and the EternalBlue/MS17-010 worm illustrate how quickly mass exploitation follows disclosure. The author warns that open-source projects face an existential dilemma: withhold patches and leave users exposed, or release them and trigger immediate automated scanning. Recommendations include mandatory back-porting of fixes and wider use of runtime protections, yet the overall outlook remains pessimistic about the coming wave of fully automated attacks.

HabrTranslated from Russian

Read at source

The security community is witnessing a dramatic acceleration in the long-standing arms race between software developers and attackers, driven by the rapid adoption of artificial intelligence. Drawing an analogy from the evolution of high-frequency trading, the researcher explains how initial simple algorithmic advantages gave way to hardware-level optimizations and, ultimately, to complex multi-market arbitrage. The same trajectory is now unfolding in information security.

In the past, the cycle was slow and deliberate. A developer would release a new version of software such as the wu-ftpd FTP server after extensive manual testing. A researcher would then spend days or weeks analyzing the code, locate a buffer overflow, craft an exploit, and responsibly report the issue. Only after the patch was published would the vulnerability receive a CVE identifier such as CVE-1999-0911 or CVE-2001-0550, giving administrators time to update.

Today the dynamic has changed. When a developer publishes a patch, the diff itself becomes a high-signal map of previously hidden flaws. An attacker can feed this diff to an AI model and receive a working exploit within minutes. The same process works on binary patches: after unpacking and analysis in tools such as IDA augmented with AI plugins, common remediation patterns—length checks, SQL sanitization, or removed dangerous functions—become immediately visible.

The consequences are stark. Publishing a patch now risks triggering automated exploit generation and mass scanning within hours or even seconds. Withholding the patch leaves the original vulnerability unaddressed. The situation mirrors the aftermath of EternalBlue and MS17-010, when hundreds of thousands of systems were rapidly compromised by ransomware and botnets once the exploit became public.

The author concludes that open-source projects are especially exposed because they cannot restrict patch distribution to paying customers. Developers are advised to back-port security fixes to older releases, while users should deploy runtime protections. Nevertheless, the researcher expects a new era of continuous, fully automated attacks against internet-facing services.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulnerabilities & Exploits

Telegram for Android Patches Voice Call Vulnerability Enabling Code Execution
Yandex Patches Millions of Stations After eMudhra Certificate Keys Compromised
Cisco ASA and FTD Face DoS Vulnerability in SSL VPN Already Exploited in the Wild