SlowMist published an analysis today about two high-severity PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. They have a CVSS score of 9.2 out of 10, putting them in the highest severity tier. Almost all PHP versions from 5.4 through 8.5.11 are affected. Official patches are available, and the vulnerabilities have been fixed in versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Even more alarming, details leaked ahead of time: Amazonโs threat intelligence team found that attackers had already been actively trying to exploit the vulnerabilities four days before they were publicly disclosed.
What does this have to do with our wallets? SlowMist used its scanning system MistEye to scan 1,488 crypto-related domains and found that 793 had PHP fingerprintsโmore than half. Many projectsโ official websites, airdrop claim pages, backend interfaces, and some custodial wallet services run on PHP. If a hacker uses this vulnerability to take over a project websiteโs server, they donโt need to touch the on-chain contract at all. They can simply alter the frontend and replace the receiving address. The page still looks familiar, but after you sign, your money is already in someone elseโs wallet.
By the way, Trust Wallet, BNB Chain, and PancakeSwap all issued statements today saying that PHP isnโt part of their tech stacks, so they arenโt affected. CZ also posted something today that ties in neatly with the second half of this story: AI doesnโt need to break Bitcoinโs cryptography. The real danger lies in data leaks combined with phishing and social engineering.
So how could ordinary retail users like us get caught out? There are two common ways. First, a project website is quietly altered. You go there to claim an airdrop, stake, or transfer funds. You donโt understand the signature request that pops up in your wallet, so you casually hit confirmโand your money is gone. Second, hackers take advantage of all the news to send fake security update pop-ups or fake customer support messages to phish you. They use the hype to bait youโthatโs the kind of thing CZ was talking about.
How do you protect yourself? Here are three things you can do right away. First, before visiting a projectโs official website over the next few days, check whether the project has officially stated that it has applied the patch. If it hasnโt, donโt connect your wallet to the site for now. Better to miss out than lose your funds. Second, before every signature, even if you canโt understand the whole thing, at least check whether the receiving address is one you recognize. If the address doesnโt match, stop immediately and close the page. Third, assume that anyone telling you to install a security update, upgrade your system, or โclick here to verifyโ is a scammer. Check through the projectโs official announcement channels. If there really is an update, it will be announced there. Keeping large amounts of funds isolated in a hardware wallet is especially worthwhile these days.
Before signing a transaction, do you usually check the signature details, or do you just hit confirm?
#้ฑๅ
ๅฎๅ
จ #้ฒ้้ฑผ #PHPๆผๆด #SlowMist
โโ web3 retail investor Xiao Kai
Disclaimer: This is a personal share and does not constitute investment advice. The content is for learning and discussion only. Crypto carries risks; please exercise caution when trading.