“The installer was not an installer. It was a wrapper. After generation, the ‘mysql_connector.dll’ injected a scheduled task that beaconed out every 48 hours. The beacon payload was small—just exfiltrating database table schemas and the first 100 rows of any table named ‘patient’, ‘user’, or ‘audit_log’.
The Last Download
We’ve wiped the web server. We’re rotating 1,200 user credentials. The original PHPMaker 2019 offline installer is safe. What CodeHopper had was a repackaged version—same file size, same digital certificate (stolen), different hash. Posts tagged PHPMaker 2019 Offline Installer Do...
DevDave… have you deployed that generated code yet? (No timestamp. The thread is locked.) User: System Reply: Re: PHPMaker 2019 Offline Installer THREAD LOCKED. Reason: Potentially compromised credentials. “The installer was not an installer
We caught it because the outbound connection went to a raw IP in a known C2 range. The attacker wasn’t after credit cards. They were after query patterns. They wanted to understand how our EMR thinks —the relationships between doctors, prescriptions, and diagnosis codes. The original PHPMaker 2019 offline installer is safe
PHPMaker 2019 Offline Installer Download
CodeHopper’s ‘old roommate’? His LinkedIn says he now works for a medical data brokerage.