Posts Tagged Phpmaker 2019 Offline Installer Do... Now

CodeHopper’s ‘old roommate’? His LinkedIn says he now works for a medical data brokerage.

(Archived Forum Thread) User: DevDave_84 Date: March 12, 2023 Subject: PHPMaker 2019 Offline Installer - Does anyone still have the .exe? I know this is a long shot. The official site only hosts v2023 and v2024 now. The legacy portal requires a support subscription that expired in 2021. I have a client with a legacy ASP.NET WebForms project tied specifically to PHPMaker 2019’s old MySQL connector. If I try to regenerate with v2023, the entire database layer breaks.

PHPMaker 2019 Offline Installer Download Posts tagged PHPMaker 2019 Offline Installer Do...

Don’t trust offline installers. Don’t trust forum heroes. And if you’re reading this because you’re looking for a legacy build? Build it from source or don’t build it at all.” (Auto-generated) User: Moderator Reply: Re: PHPMaker 2019 Offline Installer This thread has been archived due to a confirmed supply chain incident. All linked files have been blacklisted by 12 antivirus vendors as of today. Tag: PHPMaker 2019 Offline Installer Dangerous. End of story.

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. CodeHopper’s ‘old roommate’

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.

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. I know this is a long shot

“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’.