In October 2026, two incidents delivered the exact same lesson: attackers no longer need to break cryptography, as exploiting trust is more than enough. At Binance, according to the preliminary investigation, a single compromised engineer’s laptop was enough to move over $6,000 million. With PHP2Shell, a flaw in the PHP language itself left millions of websites exposed, even where a company’s own code was flawlessly written.
The takeaway for any organisation is direct. Today, security depends on three things: how well privileged access is protected, how thoroughly third-party software is controlled, and how quickly patches are applied.
What Happened in the Binance Attack?
On 29 October 2026, starting at 20:05 UTC, attackers drained Binance hot wallets across ten blockchains, with the vast majority of funds leaving in roughly 20 minutes. Binance estimated the total impact at around $6,300 million and managed to freeze nearly $3,000 million alongside its partners. It stands as the largest cryptocurrency theft on record: more than four times the $1,500 million lost by Bybit in February 2025.
What is most revealing is how it occurred. According to Binance’s initial investigation, it all began with a DevOps engineer’s compromised laptop. From there, the attacker reached a service container and dispatched unauthorized withdrawals. The company subsequently detected other points of intrusion, but found no evidence that private keys were leaked. Put simply, the attacker tricked Binance’s own systems into signing the transactions.
TRM Labs attributes the attack, with high confidence, to TraderTraitor, a unit linked to North Korea. Chainalysis and Elliptic point in the same direction, while the FBI confirmed its participation in the investigation. Binance announced it will cover all losses using its SAFU fund and corporate reserves.
What Is PHP2Shell and Why Does It Affect Much of the Web?
On 21 October 2026, the PHP team published emergency patches for two critical language vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. Both carry a CVSS 4.0 score of 9.2 and allow remote code execution without authentication. They affect any PHP installation handling web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed.
The scope is massive because PHP powers platforms like WordPress, Drupal, and Joomla, against which Wiz demonstrated successful attacks. The patched versions are 8.5.12, 8.4.27, 8.3.36, and 8.2.35; PHP 8.1 and earlier received no official patch.
The most concerning detail is the timing. Technical specifics leaked before the patch was released, and Amazon’s honeypot network logged an exploitation attempt on 17 October—four days before official disclosure. On that same day, 21 October, a malicious version of LiteLLM, a Python library widely used in AI projects, was available on PyPI for nearly two hours. It was published using GitHub tokens stolen from its developers.
What Do These Incidents Prove for Cybersecurity?
These are two distinct types of attacks, but both highlight the same fundamental shift. These are the four primary lessons:
- The weak link is trust, not technology. At Binance, no encryption was broken and no private keys were leaked. The attacker exploited an employee’s legitimate access. In the case of LiteLLM, stolen tokens were all it took. Attackers no longer force the door: they use keys the system recognises as valid.
- The software supply chain is also its attack surface. A company can write flawless code and still remain exposed due to a flaw in the language or a library it uses. PHP2Shell made this clear: risk resides in layers that most organisations do not control, yet rely on entirely.
- The patching window is measured in hours, not weeks. Exploitation attempts for PHP2Shell occurred before a patch even existed. Waiting for the next monthly maintenance window is no longer a viable strategy for critical vulnerabilities.
- Technical teams’ computers are critical infrastructure. A computer with access to sensitive systems deserves the same protection as a production server. North Korean-linked groups have targeted developers for years using lures like fake job offers or technical assessments, though that specific tactic is unconfirmed in the Binance case.
What Should Companies Do Now?
You do not need to be a cryptocurrency exchange to apply these lessons. Here are the measures with the highest immediate impact:
- Patch PHP immediately: Identify every server and application running PHP and update to 8.5.12, 8.4.27, 8.3.36, or 8.2.35. The PHP team warns that temporary mitigations do not block all attacks: the only permanent defence is the patch. If you are still running PHP 8.1 or earlier, plan your migration.
- Review third-party products: Palo Alto Networks confirmed that PAN-OS and Panorama are affected by PHP2Shell. Check with your vendors to see if your equipment or services rely on PHP.
- Protect privileged computers: Developer, administrator, and DevOps devices require endpoint detection and response (EDR), phishing-resistant multi-factor authentication, and least-privilege access to critical systems.
- Segregate sensitive operations: No single device should be able to authorise a high-value operation on its own. Multi-party approvals and automated limits halt what a single stolen credential could trigger.
- Control dependencies and secrets: Pin library versions, review updates before deploying, and use short-lived tokens that rotate frequently.
- Rehearse response plans: Binance managed to freeze nearly half of the stolen funds thanks to rapid coordination with partners. Having a tested incident response plan marks the difference between a contained incident and a crisis.
Conclusion: Security Begins with People and Vendors
Binance and PHP2Shell demonstrate that the question is no longer just whether your own systems are secure. What matters now is who has access to them, what software they depend on, and how quickly you can react when something fails outside your own organisation.
At Asta, we support organisations in assessing their exposure, prioritising critical patches, and strengthening their technical teams’ access. If you want to know whether your infrastructure is affected by PHP2Shell or evaluate how you protect privileged devices, contact our team.
About Our Mission in the Digital Space
Asta is a leading full-service technology and consulting agency. We’re trusted industry leaders, who are committed to advancing businesses through powerful IT. Yet, beyond our IT acumen in software, web and mobile app development, our fit-for-purpose managed IT service solutions and our ground-breaking AI and blockchain technologies – there’s something more.
At the core of everything we do is our relentless commitment to people.
Contact & Social Networks
Get in touch with us through our available social channels, and a specialized advisor will contact you to answer all your questions:
Website – Contact – Linkedin – Twitter
