MediumVulnerabilityMonitoring

SOCRadar says AI agents exploited PHP2Shell to harvest credentials

SOCRadar reports AI agents exploited PHP2Shell flaws from day one to harvest credentials; details are not confirmed, so check your PHP exposure.

Published
Exploitation
Claimed by SOCRadar in its article title (exploitation by AI agents from day one); the technical evidence is not confirmed here

What happened

According to SOCRadar, PHP2Shell was exploited by AI agents “from day one” in a credential-harvesting campaign. That is the claim in the title of its article, published 2026-11-18 (SOCRadar).

The text available to us was almost entirely page navigation and menus, not the article body. Beyond the title, the only relevant detail is that SOCRadar lists a “php2shell Checker” tool. SOCRadar describes it as identifying the PHP version behind a site and checking its exposure to the “php2shell core RCEs” (SOCRadar).

Not confirmed from the available text:

  • Any CVE identifiers for PHP2Shell.
  • Affected and fixed PHP versions.
  • How the exploitation was observed, and by whom.
  • How many systems or credentials were affected.
  • Who is behind the campaign.
  • Whether any independent source confirms the activity. Only SOCRadar carries this story.

Am I affected?

Not confirmed. SOCRadar’s title and tool description point to remote code execution issues in PHP core, but the version range is not given in the text we could read. If you run PHP on publicly reachable servers, you may be in scope. SOCRadar’s checker is presented as a way to test this (SOCRadar).

What to do now

  1. Read SOCRadar’s full article for the CVE identifiers, affected versions and indicators of compromise: SOCRadar.
  2. Identify the PHP version behind your public sites. SOCRadar says its php2shell Checker does this and reports exposure to the core RCEs.
  3. Once the CVE identifiers are confirmed, look them up on their NVD pages and in the PHP project’s own advisories. Apply the fixed version those sources name.
  4. Treat the credential-harvesting claim as unverified until you have evidence from your own logs. We do not have confirmed indicators to recommend.

Sources