CustodyStress
Archive › Documentation absent
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00403

Documentation absent — NiceHash (2017)

Constrained
Case description
NiceHash's December 2017 hack announcement did not confirm the precise BTC amount stolen, citing an ongoing investigation. Security researchers independently identified the wallet that received the stolen funds. NiceHash did not publish a forensic report explaining the attack vector until months later. Miners had no information during the critical first days about how many coins had been taken or whether further losses were possible.
Custody context
Stress conditionDocumentation absent
Custody systemExchange custody
OutcomeConstrained
DocumentationUnknown
Year observed2017
CountrySlovenia
Structural dependencies observed
Undocumented procedure
What this illustrates
Nobody had written down how to get back in. That knowledge existed only in the owner's head. Whether full access was ultimately possible is unclear, but significant delay or outside intervention was involved.
Outcome interpretation
Access remained possible, but only with delay, dependence, or significant difficulty.
Source
Publicly Reported
Evidence type
News article
Related cases involving documentation absent
193 cases involve documentation absent 512 cases involve exchange custody View archive statistics →
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case
← All cases
Framework references
Terms guide
Survives
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Single-person knowledge
Recovery depended on information or capability held by one individual who was unavailable.
Institutional dependence
Recovery depended on a third-party institution or service that was inaccessible or uncooperative.
Documentation gap
Recovery depended on instructions that were missing, incomplete, or unclear.
Authority mismatch
The person with legal authority to act did not have operational access, or vice versa.
Original text
Rate this translation
Your feedback will be used to help improve Google Translate