Cyberattack on Binance: Chronology of the Social Engineering Breach
The attackers successfully compromised Binance's infrastructure using a complex chain of social engineering attacks against company employees. The incident began in June with a phishing attempt via fake software updates.
Timeline of the Breach and Attacker Methods
In June, an employee downloaded a malicious version of Homebrew while trying to install an AI tool. Security services detected the threat in time, replaced the device, and changed credentials; however, hackers had already obtained information about members of the wallet infrastructure team.
In September, attackers contacted another engineer through a job search platform, posing as managers of a fictitious company. After two rounds of interviews, the employee was asked to download a test assignment containing malicious code onto their work computer.
- Malware replaced the pyenv development tool component
- Established a hidden connection to hacker servers
- Security systems failed to detect the threat at this stage
By October 20, through the compromised engineer's computer and Binance's internal AI tool, hackers gained access to two other employees' devices. One of them was a wallet infrastructure engineer whose computer contained a token for deploying software containers.
On October 29, attackers logged into the system via the third engineer's computer, used stolen credentials, and deployed a malicious container. A script targeting the crypto wallet transaction signing system was launched.
Earlier reports indicated North Korea's response to the incident, suggesting possible state involvement in these cyberattacks.







