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
Crypto Firms Say They Don't Use PHP After Critical PHP2Shell Flaw
Promoted from the source watch (pack copy 7r83qic5), snapshot 20261023T160435Z, queue priority 3 (mechanical selection by researcher@php.newsroom, read by the curator). Coingape: crypto firms say they do not use PHP after the PHP2Shell flaws. Restates the two flaws, both CVSS 9.2, enabling unauthenticated remote code...
What it says, as the collector read it
Crypto Firms Say They Don't Use PHP After Critical PHP2Shell Flaw
Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page ua/news/coingape/crypto-firms-say-they-dont-use-php-after-critical-php2shell, snapshot 20261023T160435Z. Copied byte for byte; every file's sha256 is in captures/20261023T160435Z/provenance.json and was re-checked against the watch's own hashes.
What the page says
_Curator's reading of the capture._
Coingape: crypto firms say they do not use PHP after the PHP2Shell flaws. Restates the two flaws, both CVSS 9.2, enabling unauthenticated remote code execution on PHP servers. A crypto-news angle.
> Two critical PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619), both rated CVSS 9.2, enable unauthenticated remote code execution on PHP servers.
_The watch reader's summary (researcher@php.newsroom, of its snapshot 20261022T181608Z, not necessarily this one):_ CoinGape (English, crypto news) reports on PHP2Shell's crypto impact. Binance co-founder CZ urged caution; BNB Chain and Trust Wallet said their stacks don't use PHP; Kraken migrated its backend to Rust in 2025; SlowMist scanned the industry's PHP assets.
Why it is here
From the promotion queue (index/promote.json, priority 3): Mentions CVE-2026-109618/109619 or php2shell: "Crypto Firms Say They Don't Use PHP After Critical PHP2Shell Flaw". Selected mechanically, not read by a person. Text also matches compromise/breach terms: check for a named organisation or cause.
Capture notes
Language en. Nothing in the page addresses an AI or hides text from a reader.
Claims that cite it
No claim cites this source yet.
Events that cite it
No timeline event cites this source yet.
The bytes
capture 20261023T160435Z · HTTP 200 · https://coingape.com/crypto-firms-say-they-dont-use-php-after-critical-php2shell-flaw/
headers.json353041bd4fd246901fb76a7f9f080af1a20bff4c1e995d3b32d46e98b5acbf96 1,330 bytespage.htmlbc64442be7ca302222fe2a56fd811773acecb04e6e37b90f8143f927df31a16f 553,890 bytesprovenance.json5ac2040b7561f6b81ca289b871372d07a1aa191f128c51e36488f638dad5baeb 1,751 bytesrendered.html48b5d859a142b0df61e59728e28241959377deba6af79b6d8446fc0d0721b6ab 554,246 bytesscreenshot.jpg76c34316883ebd06ef09131a6a4559514539fdd370a24de939c5c8392adc569a 664,467 bytestext.txtcaf9bd5b4fba62c2775e1430af753a4fe91fd04c547a397f4ccc45243a741e56 10,461 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 →