Skip to content

Institutional Crypto Custody: Why Private Key Security Is Not Enough

Crypto Market Monitor

For much of its history, cryptocurrency security has revolved around a deceptively simple principle: whoever controls the private key controls the assets. The industry’s response has been to develop increasingly sophisticated ways of protecting those keys, from cold storage and Hardware Security Modules (HSMs) to multi-signature wallets and Multi-Party Computation (MPC). These technologies remain fundamental to digital asset security, but recent incidents have demonstrated that protecting the key itself is only one part of the problem.

On 29 October 2026, Binance experienced a major security incident involving approximately $6.34 billion in impacted digital assets. In its initial investigation update published on 30 October, the exchange said the incident may have involved a compromised DevOps engineer’s laptop, which allowed an attacker to access a service container and submit unauthorised withdrawal transactions. Binance stated that it had found no evidence of compromised wallet private keys. In its subsequent response update on 3 November, it reported that approximately $2.85 billion had been frozen or intercepted, subject to reconciliation and market price volatility. The investigation remains ongoing, but the incident illustrates how systems surrounding a wallet can become an attack path even when the underlying key material has not been extracted.

Institutional investors need more than secure key storage. They need confidence in how assets are accessed, transactions authorised and operational risks managed.

A blockchain can verify signatures and transaction validity, but it cannot confirm whether an instruction came from an authorised source, was correctly approved or reflects the asset owner’s intent. These responsibilities sit within the custody infrastructure and governance arrangements surrounding private keys, making control over the entire transaction process just as important as key security.

The recurring weakness in major crypto security incidents

The September 2026 Bitget incident illustrates how weaknesses in wallet infrastructure can create substantial exposure. In its security notice published on 24 September, the exchange reported approximately $351.6 million in unauthorised transfers from some of its hot wallets. It stated that its cold wallets remained secure and that the incident was contained within portions of its hot and warm wallet infrastructure. Bitget did not speculate on the attack vector in its initial notice, making it important not to attribute the incident to a specific technical failure without further evidence. Nevertheless, the event demonstrates why institutions must assess the security of their entire wallet architecture, rather than treating cold storage as a complete solution.

The February 2025 Bybit breach raised similar questions at an even greater scale. Approximately $1.5 billion in digital assets was stolen from the exchange. The Federal Bureau of Investigation’s public attribution identified North Korean actors operating under the name TraderTraitor as responsible for the theft. Subsequent technical analysis highlighted the compromise of the transaction-signing process and the manipulation of information presented to signers. The incident demonstrated that sophisticated wallet arrangements can be undermined when the systems through which transactions are reviewed and approved are compromised.

The July 2024 WazirX incident offers another important lesson. More than $230 million was stolen from a multi-signature wallet with six signatories, five associated with WazirX and one with its wallet infrastructure provider. In its preliminary incident report, WazirX described a discrepancy between the transaction information displayed in the signing interface and the actual transaction payload. It suspected that the transaction payload had been replaced, resulting in the transfer of wallet control to an attacker. These were WazirX’s preliminary findings, and the parties involved disputed aspects of the incident. Nevertheless, the case exposed a critical limitation of multi-signature security: multiple approvals are only meaningful if the information being approved is accurate and independently verified.

Radiant Capital’s October 2024 exploit further demonstrated how the devices used by authorised signers can become a critical vulnerability. Approximately $50 million was lost after attackers compromised the devices of at least three developers, despite their use of hardware wallets and geographically distributed signing arrangements. According to Radiant Capital’s own post-mortem, the compromised devices were used to facilitate the signing of malicious transactions. The incident showed that hardware wallets can protect private key material while still being exposed to manipulation of the transaction information presented for approval.

These incidents differ in their technical details, but they share a broader implication. Security failures can occur at the point where technology, people and processes interact. A compromised endpoint, manipulated transaction interface or vulnerable backend service can undermine otherwise sophisticated cryptographic controls. The number of signatures required to move an asset is therefore only one measure of security. The integrity of the entire approval process matters just as much.

Why institutional custody requires more than wallet technology

The growing complexity of digital asset infrastructure has made it increasingly difficult to treat custody as a standalone technical function. A wallet may rely on secure cryptographic components, but its effective security also depends on the environment in which those components operate. This includes employee devices, internal networks, privileged accounts, cloud services, transaction interfaces and external technology providers.

For this reason, institutional custody should be assessed as a complete operating framework rather than a choice between different wallet technologies. MPC, HSMs and multi-signature arrangements can reduce specific risks, but they do not independently guarantee that an institution’s assets are protected against every possible attack. Their effectiveness depends on implementation quality, access governance, independent verification and the controls surrounding transaction execution.

The limitations of cryptographic technology itself were also highlighted by the BitForge vulnerability, documented as CVE-2023-33241. The vulnerability affected certain cryptocurrency wallets implementing the GG18 or GG20 threshold signature protocols. Under the conditions described in the disclosure, an attacker could potentially exploit weaknesses in the validation of cryptographic proofs to extract private key material. This does not undermine MPC as an approach, but it reinforces the importance of secure implementation, independent review and timely remediation. Distributed key management is only as strong as the cryptographic protocols and software implementing it.

The distinction between hot and cold storage is equally important. Hot wallets provide the connectivity required for regular trading, settlement and operational transfers, but their online availability creates a different risk profile from offline storage. Cold storage is designed to isolate assets from internet-connected environments, making it more appropriate for longer-term holdings. An effective custody architecture should therefore allocate assets according to their operational purpose, rather than treating all holdings as though they require the same level of accessibility.

However, simply maintaining separate hot and cold wallets is not sufficient. Institutions must understand how assets move between them, who can initiate those movements and what verification is required before a transfer is executed. High-value transfers should be subject to clearly defined approval thresholds, independent checks and restrictions on destination addresses. Where possible, the transaction information reviewed by authorised signatories should be verified independently of the system that generated the transaction request.

This is where institutional custody differs fundamentally from basic wallet management. It combines cryptographic safeguards with controlled access, transaction governance, infrastructure security and clearly assigned operational responsibilities. The objective is to prevent a single compromised device, account or individual from creating an unrestricted path to client assets.

The infrastructure behind the wallet matters

The growing overlap between Web2 and Web3 attack surfaces makes infrastructure security particularly important. Digital asset businesses rely on conventional software and network environments for identity management, cloud infrastructure, employee access, application programming interfaces and software development. Vulnerabilities in these systems can create indirect access to sensitive services even when blockchain protocols and wallet cryptography remain unaffected.

The PHP2Shell vulnerabilities reported in October 2026 are a reminder of how weaknesses in widely deployed Web2 software can create serious exposure. The vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619, were described as critical vulnerabilities that could allow unauthenticated remote code execution in affected PHP environments. This does not establish that a particular crypto exchange or custodian was compromised, nor that digital assets were stolen through these vulnerabilities. Their relevance is broader: any organisation operating exposed, vulnerable systems must consider whether those systems have access to sensitive credentials, internal services or transaction infrastructure.

A resilient custody architecture should therefore separate critical financial and wallet infrastructure from general corporate networks, restrict privileged access and continuously monitor systems for suspicious activity. Regular penetration testing, independent security assessments and clearly defined incident response procedures are equally important. Security cannot depend entirely on preventing an attack. Institutions must also be capable of identifying suspicious activity, containing its impact and restoring operations without compromising the integrity of client assets.

The role of third-party providers deserves particular attention. Custody arrangements may involve multiple technology vendors, infrastructure providers and external service dependencies. Institutions should understand where these dependencies exist, how access is governed and whether the provider can demonstrate adequate controls over its own systems. Outsourcing a technical function does not outsource the institution’s responsibility to understand the risks associated with it.

This broader approach to technology risk is increasingly reflected in financial regulation. The European Union’s Digital Operational Resilience Act (DORA), applicable since 17 January 2025, establishes requirements covering information and communication technology risk management, incident reporting, resilience testing and third-party technology dependencies. Its significance is that operational resilience is treated as a core responsibility of financial entities, rather than a separate technical consideration.

Asset segregation and governance are as important as technical security

This is where the legal structure of custody becomes particularly relevant. Institutions should understand whether client assets are held separately from the custodian’s own assets, how ownership and beneficial interests are recorded, and what legal protections apply if the custodian becomes insolvent. Technical security and legal asset protection address different risks, and both are necessary for a comprehensive custody framework.

Asset segregation is especially important because it helps distinguish the client’s property from the custodian’s proprietary assets. The relevant legal treatment depends on the jurisdiction and contractual structure, so institutions should examine the applicable legislation and custody documentation rather than relying on broad assurances about asset protection. A regulated banking framework can provide an additional layer of governance and supervisory accountability, but regulation should not be treated as a substitute for assessing the actual custody controls.

Governance must also extend to the people responsible for operating the system. A well-designed framework separates transaction initiation, approval and execution, applies multiple levels of authorisation to sensitive system changes and maintains clear audit trails. Recovery arrangements should be established in advance, with backup credentials and operational procedures protected from the same risks as the primary environment. These controls are not administrative details. They determine whether an institution can continue to safeguard assets when an individual, system or service provider becomes unavailable or compromised.

Proof of Reserves (PoR) can provide useful visibility into the assets held by a platform at a particular point in time. However, it does not independently demonstrate the completeness of liabilities, the absence of encumbrances or the integrity of transaction authorisation processes. Institutions need to evaluate the full custody arrangement, including the legal, operational and technical safeguards that support it.

Institutional adoption requires institutional custody

Recent security incidents have demonstrated that protecting private keys is only one part of safeguarding digital assets. As institutions increase their exposure to cryptocurrencies, stablecoins and tokenised assets, custody can no longer be evaluated solely on the strength of its cryptographic architecture. The more relevant consideration is whether the entire custody framework can maintain control over assets, transactions and operational risks, even when individual components are compromised.

This makes the selection of a custody partner a strategic decision rather than a technology procurement exercise. Institutions must look beyond Multi-Party Computation (MPC), multi-signature wallets and cold storage to examine how these technologies operate within a broader security framework. Transaction verification, multi-party authorisation, destination address controls and segregation of critical infrastructure are essential considerations. Equally important are the custodian’s regulatory status, legal segregation of client assets, independent assurance, operational resilience and recovery arrangements.

These safeguards address different dimensions of risk. Cryptographic controls protect signing credentials, transaction governance reduces the likelihood of unauthorised transfers, while legal and operational frameworks establish accountability and support the protection of client assets. Their effectiveness depends on how they work together, rather than the strength of any individual component. A sophisticated wallet architecture offers limited reassurance if the systems responsible for initiating and approving transactions remain vulnerable.

No custody arrangement can eliminate risk entirely. However, a well-designed institutional framework can limit the consequences of individual failures, establish clear responsibilities and provide the oversight required for managing digital assets at scale. As blockchain-based financial activity becomes increasingly integrated into traditional markets, the distinction between merely holding digital assets and safeguarding them within a regulated, accountable operating environment will become more consequential.

Ultimately, institutional adoption will depend not only on access to digital assets, but on the confidence that those assets can be securely held, controlled and transferred. The maturity of the custody infrastructure supporting that activity will be as important as the blockchain technology itself.

Frequently asked questions

What is institutional crypto custody?

Institutional crypto custody is the safekeeping and administration of digital assets through a professional custody framework. It combines private key management with transaction authorisation, asset segregation, governance, operational security and recovery procedures.

Why is private key security not enough?

Private key protection does not guarantee that a transaction is legitimate. Attackers can target employee devices, transaction interfaces, backend systems or approval workflows to manipulate how transactions are created and authorised, even without directly extracting private keys.

What is the difference between hot and cold crypto custody?

Hot custody keeps digital assets accessible through internet-connected wallet infrastructure for regular transactions and trading. Cold custody isolates signing credentials from internet-connected environments and is generally used for longer-term storage. Institutional arrangements often combine both according to asset use and risk requirements.

Is MPC sufficient for institutional digital asset security?

No. Multi-Party Computation distributes cryptographic signing operations across multiple parties or devices, reducing dependence on a single private key. However, MPC must be supported by secure implementation, transaction verification, access governance, infrastructure controls and independent security assessments.

What should institutions look for in a crypto custodian?

Institutions should evaluate regulatory oversight, legal asset segregation, hot and cold storage architecture, HSM or MPC technology, multi-party transaction authorisation, destination address controls, independent audits, infrastructure security, incident response and disaster recovery.

Disclaimer – Research and Educational Content 

This document has been prepared by AMINA Bank AG (“AMINA”). AMINA is a Swiss licensed bank and securities dealer with its head office and legal domicile in Switzerland. It is authorised and regulated by the Swiss Financial Market Supervisory Authority (“FINMA”). 

This document is published solely for educational purposes; it is not an advertisement nor a solicitation or an offer to buy or sell any financial investment or to participate in any particular investment strategy. This document is for publication only on AMINA website, blog, and AMINA social media accounts as permitted by applicable law. It is not directed to, or intended for distribution to or use by, any person or entity who is a citizen or resident of or located in any locality, state, country or other jurisdiction where such distribution, publication, availability or use would be contrary to law or regulation or would subject AMINA to any registration or licensing requirement within such jurisdiction. 

Research will initiate, update and cease coverage solely at the discretion of AMINA. This document is based on various sources, incl. AMINA ones.  In preparing this document, AMINA may have made limited use of artificial intelligence–enabled tools to assist with research, summarisation, and drafting, with all content subject to human review and validation. 

No representation or warranty, either express or implied, is provided in relation to the accuracy, completeness or reliability of the information contained in this document, except with respect to information concerning AMINA. The information is not intended to be a complete statement or summary of the subjects alluded to in the document, whereas general information, financial investments, markets or developments. AMINA does not undertake to update or keep current information. Any statements contained in this document attributed to a third party represent AMINA’s interpretation of the data, information and/or opinions provided by that third party either publicly or through a subscription service, and such use and interpretation have not been reviewed by the third party. 

Any formulas, equations, or prices stated in this document are for informational or explanatory purposes only and do not represent valuations for individual investments. There is no representation that any transaction can or could have been affected at those formulas, equations, or prices, and any formula(s), equation(s), or price(s) do not necessarily reflect AMINA’s internal books and records or theoretical model-based valuations and may be based on certain assumptions. Different assumptions by AMINA or any other source may yield substantially different results. 

Nothing in this document constitutes a representation that any investment strategy or investment is suitable or appropriate to an investor’s individual circumstances or otherwise constitutes a personal recommendation. Investments involve risks, and investors should exercise prudence and their own judgment in making their investment decisions. Financial investments described in the document may not be eligible for sale in all jurisdictions or to certain categories of investors. Certain services and products are subject to legal restrictions and cannot be offered on an unrestricted basis to certain investors. Recipients are therefore asked to consult the restrictions relating to investments, products or services for further information. Furthermore, recipients may consult their legal/tax advisors should they require any clarifications. 

At any time, investment decisions (including, among others, deposit, buy, sell or hold investments) made by AMINA and its employees may differ from or be contrary to the opinions expressed in AMINA research publications. 

This document may not be reproduced, or copies circulated without prior authority of AMINA. Unless otherwise agreed in writing, AMINA expressly prohibits the distribution and transfer of this document to third parties for any reason. AMINA accepts no liability whatsoever for any claims or lawsuits from any third parties arising from the use or distribution of this document. 

©2026 AMINA, Kolinplatz 15, 6300 Zug 

Share this article

Authors

Dhruvang Choudhari

Crypto Research Analyst AMINA India

Subscribe to AMINA Research

Subscribe to AMINA Research for our latest perspective.

More Research

Notice for UK visitors

AMINA Bank AG (AMINA) is a Swiss bank, authorised and regulated by the Swiss Financial Market Supervisory Authority (FINMA). AMINA’s products and services are only licenced in Switzerland. They are not registered or approved outside of Switzerland. Your IP address indicates that you are attempting to access AMINA’s website from the UK. If you want to explore AMINA’s products and services that are available in the UK, you can do so by accessing AMINA’s UK specific website.

Please click “Continue” to do this. If you don’t want to continue to the UK version of AMINA’s website, please click on “Back”.