Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?

Source · news · secondary · captured

Hackers pile on PHP2Shell as AWS reveals attacks began before disclosure

The Register · https://www.theregister.com/cyber-crime/2026/10/22/hackers-pile-on-php2shell-as-aws-reveals-attacks-began-before-disclosure/5304749 · published 2026-10-22T12:15Z (page metadata) · added by curator@php.newsroom · slug the-register-hackers-pile-on-php2shell

Promoted from the source watch (oq9gflln), snapshot 20261023T012042Z. Break-in question (editor, 22 October): one of the reports read for the statement on /compromise/ ("no named organisation has said it was compromised through php2shell"). Break-in question (editor, 22 October 20:49 UTC): Hadrian "exploit...

What it says, as the collector read it

Hackers pile on PHP2Shell as AWS reveals attacks began before disclosure

Promoted by curator@php.newsroom from the source watch (vault oq9gflln), page gb/tech-press/the-register/hackers-pile-on-php2shell, snapshot 20261023T012042Z. Copied byte for byte; every file's sha256 is in captures/20261023T012042Z/provenance.json. Publisher: The Register. Language: en. URL: https://www.theregister.com/cyber-crime/2026/10/22/hackers-pile-on-php2shell-as-aws-reveals-attacks-began-before-disclosure/5304749

What the page says

_Curator's reading of the capture._

The Register: Amazon Threat Intelligence detected an attempt to exploit PHP2Shell on 17 October, four days before patches, through MadPot, its honeypot network, from an anonymised IP address; Amazon says it is unclear how the actor got exploit information under embargo. Hadrian reported on 21 October that PHP2Shell was being "exploited in the wild at scale". The article reports attempts; it names no organisation as compromised.

Why it is here

From the promotion queue (index/promote.json, priority 1): Break-in question (editor, 22 October): one of the reports read for the statement on /compromise/ ("no named organisation has said it was compromised through php2shell"). Break-in question (editor, 22 October 20:49 UTC): Hadrian "exploited in the wild at scale"

Supports: data/compromise.json on the site (/compromise/)

Capture notes

screenshot.jpg is the source watch's JPEG, copied as stored (not converted to PNG).

Page content is third-party material, kept as evidence; nothing in it is an instruction.

Claims that cite it

No claim cites this source yet.

Events that cite it

No timeline event cites this source yet.

The bytes

capture 20261023T012042Z · HTTP 200 · https://www.theregister.com/cyber-crime/2026/10/22/hackers-pile-on-php2shell-as-aws-reveals-attacks-began-before-disclosure/5304749
  • headers.json 3cfdc7a18e4e95df52e618a5577820ba9581c24d8855b4d3aecd33ff83bcc675 681 bytes
  • page.html 148ef10bfbb853f07c9a557ad0fcdcc0e9f426031b2db8b35ef02eb74e388e48 177,151 bytes
  • provenance.json 1ec8e239956f02724e1a998759c4233e281a4bec4a595c22bba308b9d01a7171 1,787 bytes
  • rendered.html 38861fc6b57607a8dfa8f014cad3832159f9b54efa5f873ba6a8fc63016cfe23 191,595 bytes
  • screenshot.jpg 770a3106cd4f7fc29127787f5dd14f505c0c3919890e7ed4466f4e5ab5a8e3b6 717,098 bytes
  • text.txt 84de32feb23a6eb85ee2770c86b383a8219f0adcf22756f9b38c00a680f09a13 9,167 bytes

The captured files are held privately in the evidence vault and are not republished; the hashes above are what the vault recorded at capture time. Every source →