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

バルテック、サイバー攻撃によりサービス停止、情報流出の可能性（記事訂正） - INTERNET Watch

INTERNET Watch (Impress) · https://internet.watch.impress.co.jp/docs/news/2150396.html · published 2026-10-22 (corrected later the same day) · added by curator@php.newsroom · slug impress-watch-valtec

Promoted from the source watch (oq9gflln), snapshot 20261022T191433Z. Valtec blamed php2shell, then corrected: its own service's flaw (resolved, not PHP)

As of 14:40 UTC on 25 October, no named organisation has s…INTERNET Watch

What it says, as the collector read it

バルテック、サイバー攻撃によりサービス停止、情報流出の可能性（記事訂正） - INTERNET Watch

Promoted by curator@php.newsroom from the source watch (vault oq9gflln), page jp/tech-press/impress-watch/valtec-php-attack, snapshot 20261022T191433Z. Copied byte for byte; every file's sha256 is in captures/20261022T191433Z/provenance.json. Publisher: INTERNET Watch (Impress). Language: ja. URL: https://internet.watch.impress.co.jp/docs/news/2150396.html

What the page says

_Curator's reading of the capture._

INTERNET Watch (Impress) reports that Valtec (バルテック), which provides business telephone services, announced on 22 October that it suffered unauthorised access, halted part of its services and that users' personal data may have leaked. The article was corrected: Valtec issued a correction saying its first statement that the cause was "a cyberattack targeting the PHP vulnerability" was wrong, and that "a vulnerability in our own service" was exploited; it had confused the two because it was handling the PHP vulnerability at the time. INTERNET Watch changed the article's title accordingly. Valtec planned recovery within 26 October.

> バルテックでは訂正発表を行い、第一報時点で原因としていた「PHPの脆弱性を標的としたサイバー攻撃」は誤報であり、「我々のサービス自体の脆弱性」を突かれたものであると訂正した。PHPの脆弱性に関する対応を行っていたため混同したとしている。

_Curator's translation:_ Valtec issued a correction: the "cyberattack targeting the PHP vulnerability" given as the cause in its first report was wrong; "a vulnerability in our service itself" was exploited. It says it confused the two because it was handling the PHP vulnerability.

Why it is here

From the promotion queue (index/promote.json, priority 1): Valtec blamed php2shell, then corrected: its own service's flaw (resolved, not PHP)

Supports: contradictions/compromise-valtec.json

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

ClaimWho says itStatusFact-checkPrimarySources
As of 14:40 UTC on 25 October, no named organisation has said it was compromised through php2shell. Exploitation attempts are widely reported, in millions; Hadrian reports exploitation at scale and Patchstack received reports of incidents from hosting partners, neither naming a victim, and Patchstack's own telemetry showed only probing. Sophos withdrew an earlier success claim: its data showed scanning and a few failed attempts.
A time-bounded absence, not a confirmed fact: it can only be true as of the last check, and it will change. Changed from "confirmed" on 22 October at the editor's request. Refreshed by the journalist on 24 October against the evidence vault at 1f38e70921b2: the named cases (GMO, ČVUT, DMM, Valtec) are now in the vault, and none of them states php2shell as the cause (Valtec retracted). The PHP Foundation's executive director: "to our knowledge, there has been no successful attempt at remote code execution" (The Verge). Luxembourg: no institution has announced an intrusion (Paperjam). Patchstack: incidents reported to it by hosting partners (Recorded Future) against "only probing attacks, with no hard evidence of breaches yet" in its own telemetry (PCMag); on the board for the fact-check desk. An anonymous startup owner's claim of stolen source code (Fortune) is unnamed and not attributed to the flaw. Sophos, via Cyber Security News: a correction at 21:21 UTC on 22 October withdrew an earlier success claim; scanning and a small number of failed attempts, a Mirai-derived payload blocked. American Banker, 23 October: no US bank or credit union has publicly reported a compromise. Refreshed on 24 October at 16:05 UTC against the vault at 8c16a64a7cf6 (382 sources): no new source names an organisation compromised through php2shell; Die Presse (12:03 on 23 October) knows of no successful attack in Austria, and RainForest's honeypot (VOIX) records attempts only. Refreshed again on 25 October at 09:35 UTC (09:35 GMT: the UK clocks went back at 01:00 UTC that day; an earlier version of this note said 10:35 BST, which was wrong) against the vault at 87795d121200 (418 sources): still no new source names an organisation compromised through php2shell; Turkey's Presidency Cybersecurity Directorate says the e-Devlet portal had no problem. Refreshed on 26 October against the vault at 94352a55fbaa (454 sources, latest capture 14:40 UTC on 25 October): 16 new claims reviewed, still no new source names an organisation compromised through php2shell; La Razón (23 October) knows of no successful execution.
fact timeline →		this site, from every captured source in the evidence vault (454 sources, head 94352a55fbaa), as of its latest capture at 14:40 UTC on 25 OctoberreportedA4 Corroborated6/24CISA CISA Huntress Amazon SecurityWeek SecurityWeek Recorded Future Imperva Threat Research Weird Gloop Paperjam PCMag IT Social Lupa.cz Yahoo! News Japan 産経ニュース INTERNET Watch The Verge Cyber Security News American Banker The Next Web Die Presse voix Haber.com La Razón

Events that cite it

No timeline event cites this source yet.

The bytes

capture 20261022T191433Z · HTTP 200 · https://internet.watch.impress.co.jp/docs/news/2150396.html
  • headers.json 58df97fc9062fc234eef8d1d1582710ea444eb72b939acee668cee7c988492b9 286 bytes
  • page.html 54dca16481319543e0f7f4de7c4bfffb04af2e3ea7b963baa4ea5b6dd06212e0 112,513 bytes
  • provenance.json 29864193cb9702d80c121e6d555f57f9562b46db8d07df01587de8e5986dbc2e 1,664 bytes
  • rendered.html f241ae871799c4086033623f373f304027ad469bdaad5687cf3e21e58e636e88 408,910 bytes
  • screenshot.jpg d0eb4e865c0189bf912fa7f318a5e994d85516c9b51f582289ae00be950d916a 829,142 bytes
  • text.txt 8eb3458dda2e5e8f5ae7763944d9c1d9fe1733285b87b6b21481c02b28d7fd76 12,992 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 →