install script

The PHP PEAR go-pear.phar Backdoor

Updated 5 Oct 2026 · Incident date 20 Dec 2018

The official go-pear.phar PEAR installer was replaced with a tampered copy that opened a Perl reverse shell after 20 December 2018.

The copy on pear.php.net opened a reverse shell to 104.131.154.154. The same file on GitHub was not affected.

What happened

Attackers changed files on the pear.php.net server.

  • They planted a tampered go-pear.phar after the 20 December 2018 release.
  • The code started a Perl reverse shell to 104.131.154.154.
  • The code needs a shell and Perl on the system.
  • Systems that installed PEAR automatically had the greatest exposure.

The PEAR team announced the breach on 19 January 2019. The exposure window possibly reached back six months.

Affected versions

  • The copy of go-pear.phar served from pear.php.net. It is not a numbered release.
  • Exposure: after 20 December 2018 until the site went offline in mid-January 2019.
  • Clean source: GitHub pear/pearweb_phars, release 1.10.10.

Indicators of compromise

  • MD5 of the tampered go-pear.phar: 1e26d9dd3110af79a9595f1a77a82de7
  • Reverse shell address: 104.131.154.154
  • Domain bestlinuxgames.com, linked to the address by one source only.
  • A Perl process with a network connection to that address.

How to check

Hash any go-pear.phar file you downloaded. On macOS use md5 -r instead of md5sum.

find / -name go-pear.phar -exec md5sum {} + 2>/dev/null

Check logs for the address.

grep -r "104.131.154.154" /var/log 2>/dev/null

What to do now

  1. If the hash matches, treat the server as compromised and investigate it.
  2. Download a clean go-pear.phar from GitHub. Check the hash and GPG signature.
  3. Block the reverse shell address at your firewall.

Frequently asked questions

What happened to go-pear.phar?

A tampered copy on pear.php.net started a Perl reverse shell. The PEAR team announced the breach on 19 January 2019.

How do I check my go-pear.phar?

Compute its MD5 and compare it with the hash above. If it matches, treat the server as compromised.

Sources

  1. rapid7.com/blog/post/2019/01/22/php-extension-and-application-repository-pear-compromise-what-you-need-to-know/
  2. thehackernews.com/2019/01/php-pear-hacked.html

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library