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

バルテック、サイバー攻撃によりサービス停止、情報流出の可能性（記事訂正） - 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.