PHP2Shell Exploitation Observed Four Days Before Patch

· Original article ↗

Summary

An Amazon honeypot recorded PHP2Shell exploitation attempts on Oct. 17, four days before fixes arrived; no successful compromise had been publicly confirmed. The article examines shrinking exploit windows and urges pre-disclosure hunting, asset inventory and exposure-re

Key points

  • An Amazon honeypot captured PHP2Shell exploitation activity on October 17; the fix arrived October 21. No successful compromise had been publicly confirmed at the time of writing.
  • Mandiant’s figures put the average exploit warning period at minus seven days in 2025, compared with roughly two months in 2018–19.
  • The article says AI models helped researchers examine PHP code and adapt working exploits across versions and applications; human researchers still directed and reviewed the work.
  • Researchers reported Node2Shell in Google’s Brotli decompression library; the article says the library was bundled in Node.js, Bun, Linux distributions and Python packages.
  • The article recommends investigating activity from before a vulnerability’s disclosure, tracking bundled libraries, reducing internet exposure and preparing responses for periods before patches exist.
  • It also recommends hunting for post-exploitation signs, including web servers spawning shells, unexpected files in web directories and unusual outbound connections.

Article Details

Topic
Pre-patch exploitation and shrinking vulnerability-response windows, illustrated by PHP2Shell and AI-assisted vulnerability discovery.

MITRE ATT&CK

CVE

People

Malware

Products

Tools

Countries

Industries

Related Articles