UTC / SOURCE AND TIME AUTHORITY MATTER

One disclosure, several clocks

Follow the wider incident from discovery to disclosure, then compare the separate sensor reports. Each entry names its source and the kind of timestamp it provides. Early Chainguard first-availability timing remains unresolved.

PHP2SHELL / RESEARCH CHRONOLOGY / UTC

PHP2Shell: disclosure and detection

Major events, embargo concerns, early detections, and linked delivery activity

Grouped chronology; spacing is not elapsed time. Ranges may overlap.

Disclosure / embargoOther sensorsDeception Check
2024 / AUG 2026

Discovery is not public disclosure

  1. 2024
    DISCLOSURE / EMBARGOFirst OOM concerns identified

    Foundation account: no concrete RCE vector established then. [1]

  2. 11 AUG 2026
    DISCLOSURE / EMBARGOCalif privately reports RCE

    Private proof of concept supplied August 14. [2]

17 OCTOBER

Earlier activity reported elsewhere

  1. DAY PRECISION
    OTHER SENSORSAWS reports an exploitation attempt

    MadPot telemetry report; real-world success and exploit acquisition unresolved. [3]

20 OCTOBER

Embargo coordination disrupted

  1. 03:38:56
    DECEPTION CHECKShared script destination in earlier HTTP input

    The same destination appears later in our October 22 PHP-tagged request. This is HTTP traversal input, not an October 20 PHP2Shell observation. [13]

  2. ~15:00
    DISCLOSURE / EMBARGOCVE identifiers circulate

    Foundation: initially without technical detail. [1]

  3. 19:30
    DISCLOSURE / EMBARGOPHP warning; release advanced one day

    Original target October 22, 14:00 → October 21, 14:00. [1][11]

  4. ~20:00 / ~23:00
    DISCLOSURE / EMBARGODemonstration video, then private mitigation advice

    Foundation reports accidental video publication; further advice leakage only possible. [1]

21 OCT / EARLY

Attempts and patched-image reports

  1. ~02:00–08:00
    OTHER SENSORSAWS reports PoCs and additional attempts

    Source-reported interval; AWS leaves real-world success unresolved. [3]

  2. 06:07:42 / 06:18:17
    DISCLOSURE / EMBARGOAvailability claim; Chainguard CEO acknowledges early release

    HN platform times date statements, not first registry publication. CEO cites exploitation reports. [4][5]

  3. 06:17:04 / 07:24:56
    DECEPTION CHECKLinked delivery endpoint appears over SSH and telnet

    Both routes name the same endpoint later used in the October 22 sender-tagged PHP request, showing its reuse across delivery methods. [13]

  4. 07:41
    DISCLOSURE / EMBARGOFoundation's time for early patched images

    Disputed first-availability chronology: earlier statements already existed. Exact first registry time unverified. [1]

21 OCT / PROBES

Separate sensor observations

  1. 08:36
    OTHER SENSORSELLIO reports its first labelled request

    ELLIO identifies this as self-labelled PHP2Shell traffic. [6]

  2. 08:37–08:52
    OTHER SENSORSVulnCheck reports 85.11.167.243 probes

    Exact source and early user-agent overlap with our selection. [7]

  3. 08:42:42
    DECEPTION CHECKOur earliest selected labelled upload probe

    Sensor timestamp 08:42:42.137613. Before advisories, after leaks and early patch reports. [12]

21 OCT / RELEASE

Publication and the planned target differ

  1. 13:31 / 13:33
    DISCLOSURE / EMBARGOTarballs, then website announcements pushed

    Times from the PHP release manager's account, not independent deployment measurements. [8]

  2. 13:34:13 / 13:34:25
    DISCLOSURE / EMBARGOOfficial GitHub advisories published

    Platform metadata: stale state, then OOM corruption. [9][10]

  3. 13:35
    DISCLOSURE / EMBARGOFixed and source-backport branches pushed

    Release-manager account. Repository object creation times are not public release times. [8]

  4. 14:00 · PLANNED
    DISCLOSURE / EMBARGOAdvanced coordinated release target

    Not the first public advisory timestamp or first availability of every package. [11]

  5. 14:15–14:24
    OTHER SENSORSVulnCheck reports 45.198.224.169 probes

    Our selected observation from this address is the following day. [7]

22 OCTOBER

Later inputs in our retained selection

  1. 21:53:19 / 21:54:17
    DECEPTION CHECKTwo PHP-bearing filename uploads

    Separate Extensive VC inclusion pattern (CVE-2023-0159), not PHP2Shell. [12]

  2. 21:55:25
    DECEPTION CHECKFirst retained PHP-tagged downloader request

    Same destination across HTTP, SSH, telnet, and PHP; one source overlaps SSH and PHP. RedTail-consistent delivery, with no script sample acquired. [12][13]

Source labels distinguish disclosure accounts, other sensor reports, and our observations. Chronology and shared destinations do not establish execution or operator identity. Requests and sessions are separate units.
SOURCE KEY [1] PHP Foundation · [2] Calif chronology · [3] AWS MadPot · [4] HN availability statement · [5] Chainguard CEO statement · [6] ELLIO observations · [7] VulnCheck observations · [8] PHP release-manager account · [9] Stale-state advisory · [10] OOM advisory · [11] PHP advance notice · [12] Our selected event index · [13] Our selected shared-delivery evidence

Open the full-resolution timeline image · Expanded chronology and sources

Expanded source ledger

Download timeline JSON · All 26 selected request records

Swipe the timeline horizontally to read event details and source links.

Time UTCEvent and evidence typeScope and source
2024 (exact date unspecified)First signs of the OOM problem found
discovery account
Theoretical exploitation concern then, not a demonstrated RCE vector left knowingly unfixed.
Source
year, Foundation account
2026-08-11Calif reports initial RCE
third-party account
Private vulnerability reporting, not public exploit publication.
Source
day, researcher account
2026-08-14Calif supplies private RCE proof of concept
third-party account
PHP confirmation reported August 15.
Source
day, researcher account
2026-10-17AWS reports an exploitation attempt
third-party telemetry
AWS leaves real-world success and exploit acquisition unclear.
Source
day, AWS telemetry report
2026-10-20 03:38:56.597539Shared script destination in earlier HTTP input
first-party shared-delivery observation
HTTP traversal input names the same destination later submitted in our October 22 sender-tagged PHP request. The connection is the destination, not evidence of PHP2Shell use on October 20.
Source
microsecond string, sensor-recorded
2026-10-20 ~15:00CVE identifiers circulate
disclosure account
Initial leak described as nontechnical.
Source
approximate, Foundation account
2026-10-20 19:30PHP warning; release advanced by one day
disclosure account
New target October 21, 14:00; original October 22, 14:00.
Source
minute, Foundation account
2026-10-20 ~20:00Accidental demonstration video
disclosure account
Limited technical details; copies reportedly circulated.
Source
approximate, Foundation account
2026-10-20 ~23:00Mitigation guidance shared privately
disclosure account
Possible further leakage, not established.
Source
approximate, Foundation account
2026-10-21 ~02:00 to 08:00AWS reports PoCs and more attempts
third-party telemetry
None of its six published source IPs matches our selected five.
Source
approximate, AWS account
2026-10-21 06:07:42Public comment reports patched-image availability
timestamped statement
Dates the statement, not first registry publication or image contents.
Source
second, HN platform metadata
2026-10-21 06:17:04.639046Linked delivery endpoint appears over SSH
first-party shared-delivery observation
This SSH input names the same endpoint later used in the October 22 sender-tagged PHP request. The time marks the first retained vector-bearing curl fragment; the preceding host-bearing SCP fragment is 06:17:04.630082. Across the selected evidence window: 21 loader sessions from 2 sources, not 21 proven executions.
Source
microsecond string, sensor-recorded
2026-10-21 06:18:17Chainguard CEO acknowledges early release
first-party statement
Cites exploitation reports; underlying evidence not supplied there.
Source
second, HN platform metadata
2026-10-21 07:24:56.429853Linked delivery endpoint appears over telnet
first-party shared-delivery observation
This telnet input names the same endpoint later used in the October 22 sender-tagged PHP request, extending the linked activity across delivery methods. Across the selected evidence window: 16 loader sessions from 15 sources. Parser-split input is not proof of execution. HTTP requests and SSH/telnet sessions are different units and must not be summed as attacks or infections.
Source
microsecond string, sensor-recorded
2026-10-21 07:41Foundation's time for early Chainguard images
disputed first-availability chronology
Earlier statements predate this. First registry publication remains unverified.
Source
minute, Foundation account
2026-10-21 08:36ELLIO reports its first labelled request
third-party telemetry
Self-labelled PHP2Shell request. No exact source-IP overlap with our selected cohort established here.
Source
minute, ELLIO telemetry report
2026-10-21 08:37 to 08:52VulnCheck sees 85.11.167.243 probes
third-party telemetry
Exact source and early user-agent overlap with our selection.
Source
minute, VulnCheck telemetry report
2026-10-21 08:42:42.137613Our first selected labelled upload probe
first-party observation
85.11.167.243; body retained as capture placeholder, not exploit validation.
Source
microsecond string, sensor-recorded
2026-10-21 13:31Public release tarballs pushed
release-manager account
Push chronology attributed to Daniel Scherzer; activity views not independently retrieved.
Source
minute, release-manager account
2026-10-21 13:33Website announcement repository pushed
release-manager account
Not an exact independent measurement of php.net deployment.
Source
minute, release-manager account
2026-10-21 13:34:13Stale-state advisory published
platform publication metadata
4h51m30.862387s after our first selected request.
Source
second, GitHub published_at
2026-10-21 13:34:25OOM advisory published
platform publication metadata
4h51m42.862387s after our first selected request.
Source
second, GitHub published_at
2026-10-21 13:35Fixed and backport branches pushed
release-manager account
Git object author/tag dates are not first-publication evidence.
Source
minute, release-manager account
2026-10-21 14:00Advanced coordinated release target
planned event
Do not substitute this deadline for exact advisory or package publication.
Source
scheduled deadline
2026-10-21 14:15 to 14:24VulnCheck sees 45.198.224.169 probes
third-party telemetry
Our selected request from this address is the next day, not this same event.
Source
minute, VulnCheck account
2026-10-22 21:53:19.178708 and 21:54:17.455252Our two filename-injection uploads
first-party observation
Separate Extensive VC inclusion pattern using options[template], documented as CVE-2023-0159. Not PHP2Shell.
Source
sensor-recorded
2026-10-22 21:55:25.787307First retained PHP-tagged downloader request
first-party observation
Same delivery host/path as earlier HTTP, SSH, and telnet inputs. Source 77.90.185.20 also appears in SSH. This dates our retained observation, not the first adoption of the vector. The delivery pattern is RedTail-consistent; the script was not retrieved.
Source
sensor-recorded

Source notes: tarball/site/branch times are attributed to the release manager. Public activity views could not be independently retrieved. A Git commit or tag creation date is not a release timestamp. Our timestamp precision is the stored sensor string, not demonstrated measurement accuracy.