Security

PHP Webshells on Linux: Cookie-Controlled Evasion

3 min read

Summary

Microsoft warns that threat actors are using HTTP cookies to control PHP webshells on Linux hosting environments, helping malicious code stay dormant unless specific cookie values are present. The technique reduces visibility in routine logs, supports persistence through cron jobs, and highlights the need for stronger monitoring, web protection, and endpoint detection on hosted Linux workloads.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new research on a stealthy PHP webshell technique affecting Linux hosting environments. Instead of using obvious URL parameters or request bodies, attackers are using HTTP cookies as the trigger and control channel for malicious execution, making these webshells harder to spot in normal web traffic and application logs.

For security teams and administrators managing Linux-hosted web apps, this matters because the technique enables low-noise persistence, delayed activation, and more evasive post-compromise access.

What’s new

Microsoft observed multiple PHP webshell variants that all rely on cookie-gated execution:

  • Cookie-controlled activation: The webshell stays inactive unless the attacker sends specific cookie values.
  • Layered obfuscation: Some variants dynamically rebuild PHP functions and execution logic at runtime to avoid static detection.
  • Payload staging: Several samples reconstruct and write secondary payloads to disk only when the required cookie conditions are met.
  • Interactive webshell behavior: Simpler versions use a single cookie as a key to enable command execution or file upload.
  • Cron-based persistence: In one investigated case, attackers used legitimate hosting control panel workflows to register scheduled tasks that recreated the malicious PHP loader if it was removed.

Why this is harder to detect

Cookies often receive less scrutiny than request paths, query strings, or POST bodies. In PHP, cookie values are directly accessible through $_COOKIE, which makes them a convenient input channel for attackers. Combined with obfuscation and staged payload deployment, this allows malicious files to appear inert during normal traffic and activate only during deliberate attacker interactions.

Impact on administrators and defenders

For IT and security administrators, the key risk is persistent remote code execution within a compromised hosting account, even without root-level access. In shared hosting or restricted shell environments, attackers may still have enough permissions to:

  • Modify web content
  • Deploy PHP loaders
  • Recreate deleted malware through cron jobs
  • Maintain long-term access with minimal logging footprint

This can complicate remediation, especially when a “self-healing” scheduled task restores the webshell after cleanup.

Administrators should review Microsoft’s guidance and prioritize these actions:

  • Audit PHP applications and web roots for suspicious obfuscated scripts
  • Review scheduled tasks and cron jobs for unauthorized persistence mechanisms
  • Monitor cookie patterns associated with unusual server-side execution
  • Enable and investigate Microsoft Defender XDR detections and threat analytics
  • Hunt for web-accessible PHP files that write or include secondary payloads
  • Tighten file integrity monitoring and permissions in Linux hosting environments

Organizations running internet-facing PHP workloads should also ensure incident response playbooks include cron persistence checks, cookie-based webshell hunting, and follow-up validation after cleanup.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

PHP webshellLinux securityMicrosoft Defender XDRwebshell detectioncron persistence

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.