본문 바로가기
MEDIA Blogs
Media Center
2026-10-14 Blogs Crypto

DCENT Wallet Hacking Incident: Criminal Complaints and Liability for Damages

#DCENTWalletHack # DCENTWalletHacking # CryptoWalletHacking # CryptocurrencyWalletHack # CryptoAssetCompensation
Index

    Unauthorized transfers of digital assets from DCENT app wallets have raised questions about how affected users can respond to the incident and whether the wallet provider may be held legally liable.

    According to DCENT, the company received its first report of unauthorized asset transfers on September 16, 2026. As of September 17, DCENT stated that it was working with law enforcement authorities, cybersecurity specialists, and cryptocurrency exchanges to trace the transferred assets and investigate the technical cause of the incident.

    As the specific cause of the incident has not yet been conclusively determined, affected users should individually assess the possibility of filing a criminal complaint and pursuing compensation based on their wallet activity records and the movement of their digital assets.
     

    1. Overview of the DCENT App Wallet Hacking Incident


    According to DCENT's official announcement, the first report of unauthorized asset transfers was received in the early morning of September 16, 2026. Most of the users who reported losses were identified as app wallet users.

    Following the reports, DCENT notified law enforcement authorities, requested cooperation from cryptocurrency exchanges to freeze assets suspected of having been stolen, and initiated asset tracing and root-cause analysis with external cybersecurity specialists.

    However, as the technical investigation into the cause and scope of the incident remains ongoing, it would be premature to conclude that a security vulnerability in the DCENT app wallet itself directly caused the losses.

    DCENT App Wallet Incident Report

     

    2. Key Factors in Determining the Cause of the Incident


    The fact that digital assets were transferred without the user's authorization does not, by itself, establish the cause of the incident or identify the party legally responsible.

    It is necessary to examine how the affected user operated the wallet, managed recovery phrases, interacted with external services, and configured the application environment at the time of the incident.
     

    Item to Review Key Information
    Loss Details Date and time of the incident, types and quantities of assets, and estimated financial losses
    On-Chain Records Wallet addresses, recipient addresses, transaction hashes (TXIDs), and asset transfer paths
    App Environment Whether the app wallet was used, app version, updates, and transaction signing history
    Private Key Management How recovery phrases and private keys were generated, entered, stored, and managed
    External Interactions Phishing links, decentralized application (dApp) connections, and token approvals
    Reporting Records Customer support inquiries, police reports, and criminal complaint documents


    Even among users of the same DCENT wallet service, differences in recovery phrase management or connections to external dApps may lead to different technical findings and legal assessments.

    Therefore, rather than relying solely on other reported incidents, each affected user should carefully document their own wallet usage and transaction history.

     

    3. Filing a Criminal Complaint Following a Wallet Hacking Incident


    Victims of a wallet hacking incident may consider filing a criminal complaint against unidentified perpetrators and requesting that investigative authorities examine the method of unauthorized access and trace the movement of the stolen digital assets.

    Article 48 of South Korea's Act on Promotion of Information and Communications Network Utilization and Information Protection prohibits certain acts that compromise information and communications networks, including unauthorized network intrusion and the transmission or distribution of malicious software.

    However, the specific criminal offenses that may apply depend on the actual method of the attack, including how private keys were compromised, whether unauthorized system access occurred, and whether malicious software was involved.

    Criminal investigations may also be important in determining the cause of the incident, as investigative authorities may be able to obtain technical evidence and information about relevant parties that individual victims would otherwise have difficulty accessing.

     

    4. Civil Liability of the Wallet Developer or Operator


    The occurrence of a hacking incident does not automatically establish the civil liability of the wallet developer or operator.

    Where a contractual obligation has been breached, liability for non-performance of obligations may be considered under Article 390 of the Korean Civil Act.

    Where an unlawful act involving intent or negligence on the part of the operator is established, tort liability may also be considered under Article 750 of the Korean Civil Act.

    The following factors are particularly relevant when assessing potential liability for damages:

    • The scope of the operator's contractual or legal security obligations

    • Whether an actual security vulnerability existed in the application or system

    • Whether the operator was aware of the vulnerability and how it responded

    • Whether a causal connection exists between the alleged security failure and the unauthorized transfer of the user's assets

    • Whether the user's own management of recovery phrases or private keys contributed to the incident

    Ultimately, the findings of the technical investigation and any subsequent criminal investigation may provide important evidence when determining whether the wallet operator bears civil liability.

     

    5. Evidence to Preserve Following a Wallet Hacking Incident


    If unauthorized asset transfers are discovered, affected users should prioritize preserving relevant evidence rather than deleting wallet or mobile device activity records.

    The following information should be collected and organized:

    • The affected wallet address and recipient wallet addresses

    • Transaction hashes (TXIDs)

    • The date and time of the unauthorized transfers

    • The types and quantities of digital assets involved

    • Wallet screenshots and transaction histories before and after the incident

    • DCENT app version and usage history

    • dApp connections and token approval records

    • Communications with DCENT customer support, including inquiries and responses

    • Police reports and criminal complaint documents

    Recovery phrases, private keys, and wallet passwords should never be disclosed to third parties.

    DCENT has also issued official warnings regarding impersonation attempts and potential secondary scams that may arise during the investigation.

     

    6. Legal Response Strategies for DCENT Wallet Hacking Victims


    Because the circumstances and technical environments of affected users may differ, each DCENT wallet hacking case requires an individual assessment.

    In criminal proceedings, the immediate priorities are identifying the perpetrators, determining the method of unauthorized access, investigating how private keys may have been compromised, and tracing the movement of the stolen assets.

    When considering a civil claim against the wallet operator, it is necessary to establish whether a security-related failure occurred in the application or system and whether that failure caused the user's losses.

    In particular, where substantial amounts of digital assets have been lost or the stolen assets have moved through multiple wallet addresses, affected users should organize their wallet addresses, TXIDs, and other on-chain records before determining an appropriate legal response.

     

    7. Frequently Asked Questions (FAQ)

    Q1. Can I immediately claim compensation from the operator if assets disappear from my DCENT wallet?

    A claim for damages may be considered, but the occurrence of unauthorized transfers alone does not automatically establish the operator's liability.

    It is necessary to examine the technical cause of the incident, whether the operator breached any applicable obligations, and whether a causal connection exists between that breach and the losses suffered.
     

    Q2. Can I file a criminal complaint even if I do not know who the hacker is?

    Yes. Depending on the circumstances, victims may file a criminal complaint against unidentified perpetrators and request an investigation.

    In such cases, it is important to provide as much relevant evidence as possible, including the affected wallet addresses, TXIDs, asset transfer paths, and other records supporting the suspected unauthorized activity.
     

    Q3. Is it impossible to recover stolen digital assets once they have been transferred to another wallet?

    Not necessarily.

    Depending on whether the assets have entered a cryptocurrency exchange and how they have subsequently moved, it may be possible to trace the transactions or explore asset-freezing measures.

    However, actual recovery depends on the movement of the assets and the cooperation of cryptocurrency exchanges, investigative authorities, and other relevant parties.

    DCENT has also stated that it is working with relevant authorities and exchanges to trace and seek the freezing of assets suspected of having been stolen.

     

    If You Need Legal Assistance


    In digital asset wallet hacking cases, a legal assessment requires more than simply determining the amount of financial loss. The circumstances of the incident and the subsequent movement of the assets must also be examined.

    In particular, where the cause of private key exposure remains unclear or potential security failures by the wallet operator are in question, it may be necessary to consider both a criminal investigation to establish the facts and a potential civil claim for damages.

    DECENT Law Firm reviews the circumstances of each case based on the affected user's wallet addresses, transaction hashes (TXIDs), application usage records, and other relevant evidence to assess the available legal options and appropriate response strategies.