Binance Incident Crypto Safeguarding FCA Authorization

Regulatory Updates

November 16, 2026

Beyond Private Keys: What the Binance Incident Reveals about Crypto-Asset Safeguarding, Operational Resilience and FCA Authorization

What the $6.3 billion security incident tells us about operational resilience, safeguarding and the FCA’s new crypto-asset authorization regime.

The most interesting question arising from the recent Binance security incident is not simply how much cryptocurrency was stolen. It is how the attackers managed to gain access to the systems that controlled it. Did they obtain the wallet private keys? Did they penetrate Binance’s infrastructure directly? Or did they compromise an employee’s device and exploit the permissions already available to legitimate systems?

The distinction matters. Because if the emerging story is correct, it demonstrates something particularly important for the digital assets industry: The security of a crypto-asset business is only as strong as the people, processes, technology and interconnected systems through which control over its assets is exercised.

For firms preparing to enter the UK’s new regulatory framework for crypto-asset activities, this is a lesson that deserves serious attention.

What Happened at Binance?

On October 29, 2026, Binance experienced a major security incident involving unauthorized withdrawals from its hot wallets. The estimated financial impact was about $6.3 billion, involving multiple crypto-assets across several blockchain networks.

Binance’s initial investigation suggested that the attack may have originated from a compromised laptop belonging to an engineer. The attacker apparently used access obtained through that device to reach an internal service container, enabling them to submit unauthorized withdrawal instructions.

One detail is particularly revealing: Binance reported that it had found no evidence that wallet private keys had been leaked. This raises an important possibility. The attackers may not have needed to steal the private keys themselves. Instead, they appear to have compromised the systems and authorizations through which legitimate transactions could be approved and executed.

Blockchain investigators have identified the use of Ethereum’s EIP-7702 function as part of the attack. This function allows an externally owned account to delegate certain execution capabilities to smart contract code. Investigators reported that the attacker used pre-signed authorizations to redirect the behavior of an affected Binance hot wallet toward malicious code. The reported preparation of approximately 50 signed authorizations is especially interesting. By preparing authorizations covering different transaction nonce values, the attacker increased the likelihood that one would be valid when the attack was executed.

In other words, the weakness may not have been the cryptographic protection of the private key, but the integrity of the systems and processes authorized to act on behalf of the wallet. It is important to distinguish what has been established from what remains under investigation. Binance has not yet published a complete technical post-mortem, and the precise sequence of compromise remains subject to investigation.

The response has also demonstrated the importance of industry coordination. Binance has worked with blockchain intelligence firms, law enforcement and asset issuers to trace and freeze affected assets. Stablecoin issuers, including Tether and Circle, have taken action to freeze certain assets associated with the incident. Binance has also committed to absorbing the financial impact rather than passing the losses to customers.

The incident is therefore not simply a story about a vulnerability in a wallet. It is a story about access management, internal controls, transaction authorization, third-party dependencies and the ability of the wider ecosystem to respond when those controls fail.

 

The Regulatory Question: Where Does Custody Really Begin and End?

For regulators, one of the most important implications is that safeguarding cannot be assessed by looking at private key management in isolation. A firm might demonstrate it uses cold storage, multi-signature arrangements, hardware security modules, geographic separation and stringent key-management procedures. These are all relevant safeguards. But what happens if an attacker can compromise an employee’s laptop, access an internal application, manipulate a transaction-signing service or exploit an existing authorization? The private key may remain technically secure, but the assets can still be exposed.

This is precisely why regulators need to understand the full chain of control over customer assets.

The FCA’s new crypto-asset framework provides an important regulatory context. Its approach to safeguarding recognizes that control is not necessarily limited to physically holding a private key. The ability to bring about the transfer of the benefit of a crypto-asset can arise through different arrangements, including the operation of systems and the appointment of third parties.

This is particularly relevant to firms whose operating models rely on external custodians, wallet infrastructure providers, technology platforms or outsourced transaction-signing arrangements. The regulatory assessment should therefore extend beyond the question of who holds the key. It should consider who can initiate, approve, authorize, override or execute a transaction and what controls exist at each stage.

What Should Firms Preparing for FCA Authorization Be Thinking About?

The Binance incident provides a useful practical test for firms preparing applications under the new Financial Services and Markets Act (FSMA) crypto-asset regime. The question should not be whether a firm has a cybersecurity policy or a documented wallet-management procedure. It should be whether those arrangements demonstrate that the firm understands its actual exposure to operational and technology-related risks and has implemented controls proportionate to the nature, scale and complexity of its business.

There are several areas that deserve particular attention:

Private key management is only one part of the safeguarding framework.

Firms providing crypto-asset safeguarding services should be able to demonstrate a comprehensive understanding of how assets are controlled throughout their life cycle. This includes the creation, storage, use, authorization, rotation and recovery of private keys, but also the systems that interact with them.

Firms should be able to identify every component that can initiate or influence an asset transfer, including wallet-management platforms, APIs, signing services, administrative interfaces and smart contract permissions.

A particularly important exercise is to map the complete transaction-authorization chain, from the initial withdrawal request to execution on-chain. Where a firm relies on a third-party custodian or technology provider, it should understand whether that provider has the practical ability to move assets, what controls govern that ability and how the firm independently oversees the arrangement.

 

Access management and privileged permissions must be demonstrable.

The reported compromise of an engineer’s laptop highlights the risks associated with privileged access. Firms should consider whether employees have access only to the systems and information necessary to perform their roles, whether privileged accounts are subject to enhanced authentication and monitoring, and whether access can be rapidly revoked when a compromise is suspected.

Controls should address endpoint security, remote access, privileged credentials, segregation of duties and the monitoring of unusual activity.

Importantly, firms should consider the possibility that a legitimate employee account or authorized device may become the route through which an attacker gains access. The control framework must therefore be designed for the possibility of compromised legitimate credentials, not simply unauthorized external access.

 

Transaction authorization should be subject to independent controls.

The ability to initiate a transaction should not automatically confer the ability to approve and execute it. Firms should consider how they separate transaction initiation, approval and execution, and whether additional verification is triggered by unusual transaction characteristics. These might include unusually large withdrawals, changes to wallet permissions, new destination addresses, unexpected smart contract interactions or transactions that fall outside established behavioral patterns.

Multi-signature arrangements and approval thresholds can help, but they should not be treated as sufficient by themselves. If the same compromised infrastructure can influence multiple approval stages, the apparent separation may provide limited protection.

Smart contract and blockchain-specific risks need proper oversight.

The use of EIP-7702 in the reported Binance attack is a reminder that blockchain functions continue to evolve, creating new opportunities as well as new risks. Firms should understand the technical features of the networks they operate in, including account abstraction, delegated execution, smart contract permissions and upgrade mechanisms. This is particularly important for firms operating across multiple blockchain networks or offering services involving staking, decentralized finance protocols or programmable assets.

A generic cybersecurity assessment may not adequately capture these risks. Firms need access to appropriate technical expertise and a process for assessing new protocol functionality before integrating it into their operating models.

 

Incident response must be more than a documented procedure.

The ability to detect, contain and recover from an incident is as important as preventing one. Firms should be able to demonstrate how they would respond if their transaction-signing infrastructure were compromised, including the ability to suspend withdrawals, revoke authorizations, isolate affected systems and establish whether other wallets or services have been exposed. They should also consider their ability to reconcile customer entitlements, maintain accurate records, communicate with affected customers and meet regulatory notification obligations.

The Binance response demonstrates the importance of having established relationships with blockchain analytics providers, law enforcement, custodians and token issuers. Firms should test these arrangements rather than assuming they will work when needed.

 

Financial resources and recovery arrangements matter.

Binance’s commitment to cover the losses using its own resources and the Secure Asset Fund for Users raises another important consideration: What happens financially when a significant operational failure occurs? Firms should understand their ability to absorb losses, maintain operations and protect customers following a serious incident. This should form part of their broader prudential assessment, recovery planning and operational resilience framework.

The existence of insurance or a financial reserve should not be viewed as a substitute for effective preventive controls.

What Might the FCA Look for When Assessing Authorization Applications?

The FCA’s new authorization gateway represents an important shift for firms that have historically operated primarily within the money laundering registration framework. Under the FSMA regime, firms will need to demonstrate that they meet the applicable regulatory standards and can continue to do so. This is not simply an exercise in submitting policies and procedures. It requires firms to demonstrate that their governance, operational arrangements, resources and control environment are appropriate for the activities they intend to undertake.

Against the backdrop of the Binance incident, there are several areas expected to attract regulatory scrutiny.

First, does the firm genuinely understand its operating model?

The FCA will need to understand how the firm actually operates, rather than simply how it describes its business in its application. For example, a firm proposing to provide custody services should be able to explain where assets are held, who controls the means of access, which systems can initiate or authorize transactions, what functions are outsourced and how the firm oversees those arrangements. A disconnect between the firm’s stated operating model and its actual technological architecture would raise important questions.

 

Second, are the firm’s safeguarding arrangements effective in practice?

The FCA will need to assess whether the firm’s proposed arrangements provide adequate protection for customer assets. This means looking beyond private key storage to the wider control environment, including access permissions, transaction authorization, reconciliation, segregation, record-keeping, incident management and third-party oversight. The FCA’s CASS 17 safeguarding framework makes this particularly relevant for firms carrying on the regulated activity of safeguarding qualifying crypto-assets.

 

Third, is there sufficient technical competence at the board and senior management level?

The incident also raises questions about governance and accountability. Can the board understand the firm’s principal technology and cyber risks? Does senior management receive meaningful information about vulnerabilities, incidents and control weaknesses? Is there sufficient technical expertise to challenge technology providers and assess whether the firm’s controls are working?

The FCA will be interested in whether responsibility for technology and operational risk is clearly allocated, whether material issues are escalated and whether senior management can demonstrate effective oversight. It should not be sufficient for a firm to outsource its technology infrastructure and assume that accountability has been outsourced with it.

 

Fourth, are third-party arrangements properly governed?

Many crypto-asset businesses depend on external providers for custody, wallet infrastructure, cloud hosting, blockchain analytics and transaction execution. The FCA will need to understand how firms identify and manage the risks arising from these dependencies. This includes due diligence before appointment, contractual protections, ongoing monitoring, access to relevant audit and control information, concentration risk and contingency arrangements where a provider fails or becomes compromised.

The Binance incident is a useful reminder that an incident originating outside the wallet itself can ultimately compromise the assets held within it.

Finally, can the firm demonstrate operational resilience?

The FCA will need to understand how a firm would continue to operate, or safely suspend relevant activities, following a significant disruption. This includes identifying important business services, understanding dependencies, setting appropriate impact tolerances and testing the firm’s ability to respond to severe but plausible scenarios. A useful scenario for applicants to test would be the compromise of an employee’s device that provides access to privileged internal infrastructure, resulting in the potential for unauthorized customer asset transfers.

Could the firm detect the compromise? How quickly could it revoke access? Could it prevent further transactions? Could it establish which customer assets were affected? Who would make the decision to suspend withdrawals? How would customers and the regulator be informed?

These are the kinds of practical questions that can distinguish a mature control environment from one that exists primarily on paper.

 

The wider lesson: Security is an ecosystem responsibility.

One further aspect of the Binance incident deserves attention: the role of stablecoin issuers and other ecosystem participants in containing the losses. The ability of certain issuers to freeze assets demonstrates that safeguarding and incident response in digital assets are not always confined to the boundaries of an individual firm.

The ecosystem is interconnected. Custodians, exchanges, blockchain networks, stablecoin issuers, infrastructure providers and analytics firms can all have a role in identifying and responding to an incident. However, the availability of intervention mechanisms should not create a false sense of security. Not all crypto-assets can be frozen, and not all blockchain networks offer equivalent intervention capabilities.

Firms should therefore understand the extent to which their recovery arrangements depend on external parties and distinguish between controls they can exercise themselves and those that depend on third-party cooperation.

Conclusion: Authorization Requires Evidence, Not Assurances

The Binance incident is a significant reminder that sophisticated wallet security does not necessarily translate into effective asset protection. The critical vulnerability may sit several layers away from the wallet itself: in an employee’s device, an internal service, an administrative permission or an authorized process that was never designed to withstand compromise.

For firms preparing to apply for FCA authorization, the lesson is clear. Safeguarding, cybersecurity, operational resilience and governance should not be treated as separate compliance workstreams. They are interconnected elements of the same control environment. For the FCA, the challenge at the authorization gateway will be to establish whether applicants can demonstrate that these controls are not only documented but properly designed, implemented, tested and overseen.

Ultimately, the question is not simply whether a firm can protect its private keys. It is whether it can demonstrate control over everything that can move its customers’ assets.

How Kroll Can Help

Kroll brings together regulatory, cybersecurity and digital assets expertise to help firms prepare for FCA authorization and strengthen the controls that protect customer assets. Our teams support regulatory readiness assessments and operational resilience testing, helping firms identify control gaps, prioritize remediation and demonstrate effective safeguards in practice.

If you require assistance with any of these challenges or would like to learn more about how Kroll can help strengthen your authorization readiness and digital asset safeguards, please contact your usual Kroll representative or any of the contacts listed below.

Stay Ahead with Kroll

Financial Services Compliance and Regulation

In the ever-evolving financial services landscape, Kroll's award-winning team offers comprehensive regulatory and compliance services, guiding clients through registration, licensing, and compliance support to minimize risks and enhance efficiency globally.

UK Financial Services Compliance and Regulation

The UK regulatory landscape is constantly evolving, with new Financial Conduct Authority (FCA) initiatives introduced and working practices regularly updated at a European level.

Cryptocurrency Risk, Investigation and Compliance Services

Kroll is the leading global provider of crypto compliance, risk, and investigative services. Since the introduction of the first virtual asset in 2009, Kroll has worked side-by-side with crypto companies, investors, and law enforcement to help them meet their most critical challenges.

Investigations, Diligence and Compliance

Kroll’s Investigations, Diligence and Compliance team helps our clients stay ahead of complex demands related to independent expert analysis, testimony, advice and intelligence in complex investigations, litigation and projects globally.