@BalaiBB - PHP2Shell Bitcoin Honeypot Holds
@BalaiBB on X A developer left a Bitcoin wallet holding about $2,000 on a server running an unpatched PHP version vulnerable to PHP2Shell, and challenged anyone to steal it. After 17 hours the funds are untouched, though people are crashing the server, and the poster argues the bug is real but hard to actually exploit.
- The server runs PHP without the October 21 fixes for the critical PHP2Shell flaws, and the wallet holds roughly $2,000 in Bitcoin.
- After 17 hours nobody has taken the funds; attackers have only managed to crash PHP, with no remote code execution achieved.
- The poster uses it to argue that a vulnerability being real is different from it being practically exploitable, and cites Marcus Hutchins' criticism of fake AI-generated exploits on GitHub.
A developer set up a deliberately unpatched PHP server holding a Bitcoin key worth about $2,000 and invited the internet to steal it. The target is a flaw called PHP2Shell, a critical vulnerability that was fixed on October 21. The server was left vulnerable on purpose. After 17 hours the wallet still held its funds, and according to the developer, someone has been crashing PHP on the box but nobody has achieved remote code execution, the step that would actually let an attacker take control of the machine and move the coins.
The gap the post highlights is between a vulnerability existing and a vulnerability being exploitable in practice. The author says the bug is real but that turning it into working remote code execution is a much harder job, and the open wallet has become a live test of that claim. The author also ties this to an older argument: a previous post criticizing a flood of fake, AI-generated exploit proofs-of-concept on GitHub, with Marcus Hutchins's name attached to the skepticism. The poster presents the unclaimed wallet as evidence that a bug can be real on paper and still resist weaponization.
The source is a short post on X, quoting a cyber news account, so the details are secondhand and the outcome is still unfolding. The core facts are the PHP2Shell flaw, the October 21 patch date, the roughly $2,000 balance, and the 17-hour window with no successful exploit reported. Anyone wanting to verify the status of the wallet or the exploit should check the wallet's on-chain activity and the developer's own updates rather than relying on the post alone.