PHP2Shell Challenge Server Breached, Bitcoin Bounty Claimed

| 2 Min Read
A hacker exploited PHP2Shell flaws to breach a live server, revealing how multipart uploads and session handling can turn memory corruption into code execution.

A live exploit of the PHP2Shell vulnerabilities turned a Bitcoin bounty into a practical test of how difficult remote code execution can be. The winner, known as “KillaBoi,” compromised the challenge server and published a proof of concept detailing the attack.

The challenge creator, posting as “cloudlandsdev,” launched the server on October 24 to see whether anyone could use the newly disclosed PHP flaws to reach the funds. The prize began at about $502, then grew through donations to 0.02511679 BTC, valued at $2,021.22 when the win was recorded. The site logged the claim at 15:47 UTC on October 25, about 19.28 hours after the challenge began.

“Made this because I'm curious if anyone out there has figured out how to actually use this PHP RCE, we spent the last few days panicking. Have fun!” the creator wrote in the forum announcement.

From memory corruption to command execution

The vulnerabilities, CVE-2026-109618 and CVE-2026-109619, affect PHP’s request handling and memory management. In vulnerable configurations, they can let an attacker run code with the permissions of the web server account. PHP released fixes on October 21, but turning the flaws into a working attack required more than applying a public exploit to an arbitrary machine.

KillaBoi’s proof of concept on GitHub describes how multipart uploads and session data helped build the exploit. The attacker pushed a PHP worker past its memory limit, leaving internal state inconsistent. Later requests exposed memory through session cookies, revealing addresses associated with PHP’s memory structures and executable code.

With those addresses, the attacker assembled a forged PHP data structure that triggered command execution during cleanup. The final request returned evidence that the command had run inside the PHP process.

The breach didn’t directly reveal a private key matching the advertised prize address. On-chain records show the funds were later sent to an address beginning “bc1qr4” and ending “lk7a9,” which Blockonomics labels as a Kraken cold wallet.

Heavy traffic complicated the challenge

Interest in the experiment created its own operational strain. The creator said visitors repeatedly consumed the server’s available computing capacity soon after it was increased. Limited storage also meant the system couldn’t retain every log, making it harder to document the successful attack.

That’s a useful reminder for teams assessing newly disclosed flaws: a proof of concept’s existence doesn’t by itself show how easily a specific system can be compromised. Configuration, runtime behavior and available resources all shape what an attacker can achieve. Here, though, a public challenge server provided a concrete target and the winner published a detailed account of reaching code execution.

Other routes to recovering Bitcoin

Bitcoin recovery has also depended on reverse engineering rather than live exploitation. In 2024, hardware hacker Joe Grand, known as “Kingpin,” and researcher Bruno helped a wallet owner identified as Michael regain access to 43.6 BTC. Michael had forgotten a 20-character password. The researchers analyzed an older version of RoboForm’s password generator and found a flaw that made the password predictable.

They recovered the wallet in November 2023, when its Bitcoin was worth about $1.6 million. By the time the recovery was reported in May 2024, the value had risen to nearly $3 million.

In another case, a pseudonymous holder known as “cprkrn” recovered five BTC, worth roughly $400,000, in May 2026 after years without access. The owner said Anthropic’s Claude AI helped locate a December 2019 backup that could be decrypted with a password previously written in a notebook. The file contained the keys needed to access the Bitcoin.

The PHP2Shell breach lands amid pressure on security teams to patch affected installations and scrutiny over how the flaws were disclosed. A separate report on the disclosure controversy describes how premature publication disrupted the coordinated release process. The challenge’s clearest takeaway is technical: the exploit path was complex, but it worked against a live server in less than a day, giving defenders a concrete reason to check patched PHP deployments and their configurations.

Source: Newton Gitonga · www.tomshardware.com

Comments

Please sign in to comment.