网络安全
默认 25 个服务器的 Dream Reports PHP2 Shell 攻击链
在 Google 上的首选来源中添加 Unite.AI
Dream报道了一个PHP2Shell攻击链，称其称损坏了25个服务器，包括美国政府附属环境中的系统。 其10月26日的调查描述了一个被曝光的防火墙管理界面成为通向内部身份基础设施的路径。
报告的总数包括24个周边防火墙和一个内部管理服务器。 Dream扣留了受影响的供应商和软件版本，称通知了供应商。
开采链如何跨越两个安全边界
连锁配对为PHP2Shell，被跟踪为CVE-2026-109618和CVE-2026-109619，并配有Linux特权-升级脆弱性Fragnesia,CVE-2026-46300.
这些脆弱性涉及不同的障碍。 远程代码执行为攻击者提供了通过可达服务运行代码的方法。 本地特权升级之后可以将受限制的立足点变为对操作系统的控制。 将它们结合起来会改变事件应对问题：调查人员必须考虑受损的电器在自己的管理界面之外可以获取什么。
红帽将Fragnesia描述为Linux内核的XFRM ESP-in-TCP子系统中的一个缺陷。 不安全的加密处理可以让低特权的本地攻击者改变只读文件的页面缓存，覆盖特权二进制，并获得根权限。 因此，它是一个明显的升级机制，而不是最初未经认证的切入点。
梦想确认提取 LDAP 服务账户证书和目录目录目录。 它无法确定密码喷洒、试图建立后门账户或SAML签名键提取是否成功。 这些限制事项：确认的对目录信息的访问并不确立对活动目录的完全接管。
《大赦国际证据》确立的内容
调查人员发现Claude Code已安装并配置有DeepSeek和Kimi的进攻平台。 Dream 称没有直接证据表明这些工具写下了开发或开发后的脚本，也没有将操作定性为完全自主。 它所建议的中国关系是暂时的；它没有命名任何威胁演员。
对于维权者来说，这种区分将可观察到的工具与关于作者身份、经营者身份或自主性的结论区分开来。 编码助理的存在可以支持关于工作流程的假说，但它本身无法确定是哪个模型做出决策，还是由谁指挥操作。
PHP 修正和早期的开发窗口
PHP项目10月21日的咨询将PHP 8.5.12、8.4.27、8.3.36和8.2.35确定为安全发布，以固定两个关键的远程码执行弱点。 一项涉及记忆外处理，留下部分初始化的内部请求数据；另一项涉及在其支持内存被释放后存活的僵化的内部状态。
警告项目，即服务网络请求的PHP设施面临风险，对Apache的mod php配置评估风险最高。 它称部分缓解功能并不能提供完整的保护并引导用户更新。 对于被包装的电器来说，实际的补救途径取决于销售商支持的固件和回接的修复，而不只是运行时的版本字符串。
Unite.AI之前覆盖了PHP补丁和前沿AI在发现缺陷中的作用。 新报告将注意力从发现转移到暴露部署的后果。
另外，Amazon"威胁情报"报告，自10月17日起，PHP2Shell在其MadPot蜂蜜壶网络中试图进行开采，然后公开披露。 遥测不能确定是同一个操作员进行这项运动。
AWS建议在数小时内衡量关键互联网薄弱环节的缓解时间表，从已知的最早开发日期而不是披露日期开始调查，并开发不完全依赖于CVE特定签名的检测。 对于PHP2Shell，它建议至少追溯到10月17日。
梦想技术适合的地方
在其公司网站上，"梦"将"英雄"定位为支持脆弱性调查，恶意软件倒置工程，法证分析，以及验证修正的自主网络研究系统。 其互补的球面平台侧重于在政府和关键基础设施环境中绘制曝光图和优先防卫。
技术上的区别是调查一个特定的弱点和了解它在整个业务网络中的重要性。 周边电器，其管理服务器，以及身份目录可能拥有不同的所有者和补丁周期，然而攻击者可以将它们连接到一条路径。 有效遏制需要检查这条路径，同时安装相关的更新。
本文由 AI宝库自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
Cybersecurity
Dream Reports PHP2Shell Attack Chain That Compromised 25 Servers
Add Unite.AI to your preferred sources on Google
Dream has reported a PHP2Shell attack chain that it says compromised 25 servers, including systems in a U.S. government-affiliated environment. Its October 26 investigation describes an exposed firewall management interface becoming a route toward internal identity infrastructure.
The reported total comprises 24 perimeter firewalls and one internal management server. Dream withheld the affected vendor and software versions and said it notified the vendor.
How the Exploit Chain Crossed Two Security Boundaries
The chain paired PHP2Shell, tracked as CVE-2026-109618 and CVE-2026-109619, with the Linux privilege-escalation vulnerability Fragnesia, CVE-2026-46300.
These vulnerabilities address different barriers. Remote code execution gives an attacker a way to run code through a reachable service. Local privilege escalation can then turn a restricted foothold into control over the operating system. Combining them changes the incident response problem: investigators must consider what the compromised appliance could access beyond its own management interface.
Red Hat describes Fragnesia as a flaw in the Linux kernel’s XFRM ESP-in-TCP subsystem. Unsafe cryptographic processing can let a low-privileged local attacker alter the page cache of read-only files, overwrite privileged binaries, and obtain root privileges. It is therefore a distinct escalation mechanism, rather than the initial unauthenticated entry point.
Dream confirmed extraction of an LDAP service-account credential and directory enumeration. It could not establish whether password spraying, attempted backdoor-account creation, or SAML signing-key extraction succeeded. Those limits matter: confirmed access to directory information does not establish a complete takeover of Active Directory.
What the AI Evidence Establishes
Investigators found Claude Code installed and an offensive platform configured with DeepSeek and Kimi. Dream said it had no direct evidence that these tools wrote the exploit or post-exploitation scripts and did not characterize the operation as fully autonomous. Its suggested Chinese nexus is tentative; it named no threat actor.
For defenders, that distinction separates observable tooling from conclusions about authorship, operator identity, or autonomy. The presence of a coding assistant can support a hypothesis about workflow, but it cannot by itself establish which decisions a model made or who directed the operation.
The PHP Fixes and the Earlier Exploitation Window
The PHP project’s October 21 advisory identifies PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 as the security releases fixing the two critical remote-code-execution vulnerabilities. One involves out-of-memory handling leaving internal request data partially initialized; the other involves stale internal state surviving after its backing memory has been freed.
The project warns that PHP installations serving web requests are at risk, with the highest assessed risk for Apache’s mod_php configuration. It says partial mitigations do not provide complete protection and directs users to update. For packaged appliances, the practical remediation route depends on the vendor’s supported firmware and backported fixes, rather than a runtime version string alone.
Unite.AI previously covered the PHP patches and the role of frontier AI in discovering the flaws. This new report shifts attention from discovery to the consequences of an exposed deployment.
Separately, Amazon Threat Intelligence reported PHP2Shell exploitation attempts in its MadPot honeypot network beginning October 17, before public disclosure. That telemetry does not establish that the same operator conducted the campaign Dream describes.
AWS recommends measuring mitigation timelines for critical internet-facing vulnerabilities in hours, investigating from the earliest known exploitation rather than the disclosure date, and developing detections that do not depend solely on a CVE-specific signature. For PHP2Shell, it recommends looking back at least to October 17.
Where Dream’s Technology Fits
On its company website, Dream positions Hero as an autonomous cyber-research system supporting vulnerability investigation, malware reverse engineering, forensic analysis, and validated fixes. Its complementary Sphere platform focuses on mapping exposure and prioritizing defense across government and critical-infrastructure environments.
The technical distinction is between investigating a particular weakness and understanding where it matters across an operational network. A perimeter appliance, its management server, and an identity directory may have different owners and patch cycles, yet an attacker can connect them into one path. Effective containment requires examining that path alongside installing the relevant updates.
Auto-fetched and translated by AI Gem Box. All rights belong to the original author.