In‑depth explainer on hacking in crypto: key threats, North Korean state groups, DeFi and smart contract exploits, AI‑driven attacks, quantum risks, and practical defenses for users, developers, and institutions.
+10 sources across the wider coverage universe
Crypto security company Ledger plots $4bn New York listing. French group enjoys record year as more investors seek protection from hacking. It is working with bankers at Goldman Sachs, Jefferies and Barclays on the deal, which could take place as soon as this year, according to people familiar with the matter. They cautioned that plans could yet change.2026-01
Paradigm’s Samczsun uncovers North Korea’s broader hacking arsenal beyond Lazarus, exposing multiple advanced threat groups and tactics.2025-04
U.S. initiates forfeiture action against crypto linked to $879M thefts by North Korean military hacking groups Lazarus and APT38.2024-10
Ex-security engineer gets three years for first-ever smart contract hacking conviction, stole $12 million in crypto.
Shakeeb Ahmed just sentenced for Nirvana Finance "exploit" - he said, "I found a way to exploit a crypto exchange's smart contracts."2024-04
Four members of FIN9 Cybercrime group charged in $71M hacking case, says FBI.2024-06
Israeli spyware firm NSO hit with $167 million judgment for hacking 1,400 WhatsApp users, setting a major legal precedent.2025-05
Hacking in Crypto: Risks, Methods, and Defenses
At its core, hacking refers to the compromise of digital systems or accounts through unauthorized access, often to steal data or funds, disrupt services, or gain strategic advantage. In crypto, hacking has evolved into a high-stakes contest where attackers probe blockchains, exchanges, smart contracts, and users’ devices for weaknesses, while defenders race to harden infrastructure and invent new security models against increasingly automated, AI‑driven, and even state‑sponsored threats.
Defining Hacking in a Crypto Context
Hacking in general cybersecurity practice is commonly defined as gaining unauthorized access to a digital device, account, or network and using that access to steal data, disrupt operations, or otherwise misuse the system. While not all hacking is malicious—security researchers and “white hats” use similar techniques to test defenses—the term in common usage typically refers to illegal, harmful activity. Digital intrusions range from guessing weak passwords and exploiting software flaws through to sophisticated, multi‑stage campaigns involving custom malware, social engineering, and the abuse of trusted third‑party services. In every case, the core idea is the same: an attacker manipulates a vulnerability to make a system behave in ways its designers did not intend.
In the crypto ecosystem, hacking takes on a distinctive character because the assets at stake are digital bearer instruments secured only by cryptographic keys and on‑chain logic. A successful intrusion into an exchange’s hot wallet, a decentralized protocol’s smart contracts, or a user’s seed phrase can immediately unlock funds that can be moved globally with minimal friction and often limited recourse. The lack of central authority, the pseudonymous nature of blockchain addresses, and the irreversibility of transactions together make crypto especially attractive to cybercriminals. These same properties, however, also leave a rich on‑chain trail that investigators can analyze, allowing firms like Chainalysis and TRM Labs to follow stolen funds across mixers, bridges, and exchanges.
Why Crypto Is Such a High‑Value Target
Crypto markets combine huge concentrations of liquid value, open‑source infrastructure, and a constant stream of experimental code, which together create a fertile environment for exploitation. Public data indicate that nearly 2.2 billion dollars in crypto assets were stolen through hacks in 2024 alone, with a single incident accounting for more than 300 million dollars. The broader 2023–24 threat landscape has been paradoxical: total funds stolen from crypto platforms fell by more than half in 2023 compared with the prior year, even as the number of distinct incidents actually rose. This pattern suggests that while some large systemic vulnerabilities have been patched, the attack surface is fragmenting into a long tail of smaller protocols, bridges, and services that attackers continue to probe.
The appeal for adversaries is reinforced by how easily stolen crypto can be laundered, especially when routed through decentralized exchanges, mixers, privacy coins, and cross‑chain bridges. North Korea‑linked groups, for instance, stole approximately 577 million dollars in just two attacks in 2026—on Drift Protocol and KelpDAO—representing about seventy‑six percent of all hack losses in crypto up to that point in the year. Because transactions are settled globally within minutes and cannot be reversed, defenders must identify and stop intrusions as they unfold; by the time a hack is detected, the funds are often already spreading through a complex web of on‑chain hops designed to frustrate tracing. This combination of liquidity, programmability, and instant settlement makes crypto a uniquely tempting target compared with traditional bank systems that have more friction and human oversight.
Core Concepts: Vulnerabilities, Exploits, and Threat Actors
To understand hacking in crypto, it is useful to distinguish between vulnerabilities, exploits, and threat actors. A vulnerability is a weakness in a system’s design, implementation, or operation that could allow an attacker to violate its security assumptions. In smart contracts, vulnerabilities might include reentrancy bugs that allow repeated withdrawals, arithmetic overflows that corrupt balances, or misconfigured access controls that expose administrative functions to anyone. In user endpoints, vulnerabilities could be out‑of‑date operating systems, default router credentials, or the reuse of passwords across multiple services.
An exploit is the concrete technique or code that turns a vulnerability into an attack path. In the crypto context, exploits often take the form of precisely crafted transactions or sequences of transactions that manipulate contract state in unforeseen ways; they may also involve malware that exfiltrates private keys from infected machines, or phishing sites that capture seed phrases and two‑factor codes. Threat actors are the individuals or groups orchestrating these exploits, ranging from lone scammers and teenage crews through to organized cybercrime gangs and nation‑state units. The crypto space has seen all of these, including state‑backed teams from North Korea that combine social engineering, malware, and on‑chain obfuscation to fund the country’s weapons programs. Understanding the interplay between vulnerabilities, exploits, and adversaries is the starting point for any serious discussion of crypto security.

Crypto security company Ledger plots $4bn New York listing. French group enjoys record year as more investors seek protection from hacking. It is working with bankers at Goldman Sachs, Jefferies and Barclays on the deal, which could take place as soon as this year, according to people familiar with the matter. They cautioned that plans could yet change.


Let's build better security, that's what ledger is telling us
Readers don't click on hacking stories for exploit mechanics — they click for attribution and accountability: which nation-state is behind it, whether the DOJ seized the funds, and who finally went to prison for it.↗
The Modern Crypto Hacking Landscape
The contemporary landscape of crypto hacking is defined by four overlapping dynamics: the rise of DeFi and smart contract exploits, persistent attacks on centralized services and user endpoints, the professionalization of cybercrime markets, and the growing role of AI in scaling and refining intrusions. These dynamics do not replace earlier attack patterns like phishing and malware; rather, they layer new capabilities and targets on top of a familiar base of cyber risk. For crypto participants, this means that both “old‑school” and cutting‑edge threats must be considered simultaneously.
From a macro perspective, the raw dollar value of hacked funds has plateaued or fallen slightly, but incident counts remain high, which suggests that attackers are spreading their efforts across many smaller opportunities. Investigations by firms like Chainalysis have highlighted that 2024’s aggregate hack volumes, while still significant at about 2.2 billion dollars, did not reach the peaks of prior boom years, even as the number of individual breaches remained elevated. The reduction in large bridge exploits and catastrophic single‑protocol failures may indicate that the industry has learned from earlier disasters by hardening certain high‑value components. At the same time, mid‑tier protocols, wallet providers, and ecosystem infrastructure continue to be probed relentlessly, and even one design oversight in a multisig or admin panel can lead to eight‑figure losses.
DeFi, Smart Contracts, and Protocol‑Level Exploits
Decentralized finance relies on smart contracts—self‑executing code on blockchains like Ethereum and Solana—to replace centralized intermediaries in activities such as lending, trading, and derivatives. The composability of these contracts, which allows protocols to interact with each other like building blocks, is one of DeFi’s strengths but also a major source of systemic risk. A bug in a widely used contract, or an exploit that cascades across multiple protocols via shared liquidity pools and price oracles, can quickly propagate losses. Security firms and industry analysts have repeatedly noted that DeFi remains disproportionately represented in major hack statistics, with bridges and cross‑chain infrastructure singled out as particularly fragile links.
Recent coverage has underscored how persistent these issues are. In one analysis, executives at security firms and traditional financial institutions argued that DeFi is unlikely to win over large banks until it dramatically reduces hacks, emphasizing that critical weaknesses remain in on‑chain security and especially in the bridges that connect different blockchains. During one April, breaches were reported on twenty‑seven out of thirty days, leading a leading audit firm’s CEO to describe it as DeFi’s worst month in four years. This drumbeat of exploits—from flash loan‑enabled arbitrage attacks to permission misconfigurations in upgradeable contracts—has kept institutional allocators cautious, even as DeFi’s technological promise continues to attract developers and niche capital.
The Drift Protocol incident offers a concrete illustration of how protocol‑level design can be compromised in ways that go beyond the usual “smart contract vulnerability” narrative. According to commentary by Ledger’s chief technology officer, the Drift hack shared an identical method with a prior breach at Bybit, not through a mistake in the contract logic itself but via a compromise of the protocol’s multisignature mechanism that governed critical operations. In other words, the issue was not that the code implementing trading functions was buggy, but that the administrative controls designed to secure upgrades and withdrawals were themselves poorly protected or socially engineered. North Korea‑linked actors have been suspected in several such sophisticated operations, blending technical skill with patient reconnaissance of governance procedures and key‑holder behavior. For DeFi projects, this underscores that “on‑chain security” must encompass governance, key management, and operational processes as much as bytecode audits.
Centralized Services, Wallets, and Socially Engineered Breaches
Although DeFi exploits capture headlines, centralized exchanges, brokerages, and wallet providers remain prime targets because they aggregate significant user funds behind a single security perimeter. Over the past years, multiple centralized services have suffered wallet drains or infrastructure breaches that led to eight‑figure losses, eroded user trust, and triggered regulatory scrutiny. These incidents often arise not from novel blockchain exploits but from familiar web‑security issues: credential theft, unpatched servers, misconfigured cloud storage, or phishing of employees with privileged access. As general cybersecurity research emphasizes, hackers routinely look for “holes” in outdated software and use spoofed websites or malicious links to harvest passwords and session tokens.
End‑user wallets are another frequent point of failure, especially when users store seed phrases in plain text, reuse passwords, or install browser extensions and mobile apps from untrusted sources. Scams that compromise high‑profile social media accounts and then use them to promote fraudulent tokens have repeatedly siphoned hundreds of thousands of dollars from followers in a matter of hours. In one recent pattern, a single scammer allegedly hacked more than fifteen prominent X accounts with phishing emails and proceeded to launch meme‑coin “rug pulls” from those profiles, stealing around half a million dollars over a month. These attacks blur the line between hacking and social manipulation: technically, the underlying blockchains worked as designed, but users were enticed into signing malicious transactions or sending funds to attacker‑controlled addresses after their trust in a known personality had been hijacked.
Mining and Infrastructure Hacking
The pursuit of illicit crypto proceeds is not limited to direct theft of tokens; attackers also seize computing resources to mine coins or support broader intrusion campaigns. A case in Canada involved a Saskatchewan man accused of conspiring to hack into supercomputers at American universities for the purpose of cryptocurrency mining, leading to an extradition order to the United States. According to court filings, the suspect allegedly gained unauthorized access to powerful academic computing clusters, installed mining software, and diverted energy and processing power away from research workloads to generate personal profit. This kind of “cryptojacking” imposes real costs on institutions in the form of increased electricity bills, hardware wear, and reduced availability for legitimate users.
Beyond academic environments, mining malware has been found on enterprise servers, cloud instances, and even consumer Internet‑of‑Things devices whose default login credentials or outdated firmware made them easy targets. In some cases, such compromised infrastructure forms part of larger botnets that attackers can repurpose for credential‑stuffing, distributed denial‑of‑service (DDoS) attacks on exchanges, or mass‑phishing campaigns. In others, specialized hardware—such as modified smartphones or custom rigs designed to exfiltrate data from mobile devices—has been seized from operators suspected of both espionage and crypto theft. Our newsroom has reported on law‑enforcement actions against such “hacking vessels,” reminding users that the physical security of devices they rely on for wallet access can be as important as their digital hygiene.
Threat Actors: From State Units to Teen Crews
The range of actors involved in crypto hacking is unusually broad. On one end of the spectrum are nation‑state operators integrating crypto theft into geopolitical and military agendas; on the other are teenage gangs experimenting with stolen tools and scripts in search of quick gains. Between these extremes lie professionalized cybercrime groups that buy and sell access, exploit kits, and insider data on underground forums. Understanding these actors’ motives and capabilities helps explain why some attacks are meticulously planned over months, while others are opportunistic smash‑and‑grab operations.
Motivation typically falls into a few categories: financial gain, espionage, political disruption, and, in the case of some hacktivists, symbolic protest. Crypto is especially attractive for financially motivated actors because it offers direct monetization without the need to fence physical goods or interface with traditional banking systems. At the same time, because blockchains provide a transparent ledger of all transfers, sophisticated attackers must invest heavily in obfuscation techniques, while law‑enforcement agencies and analytics firms invest in de‑obfuscation. This arms race is particularly visible in the campaigns of North Korean groups.
North Korea’s Crypto Hacking Apparatus
North Korea’s state‑backed hacking operations are among the most studied in the crypto space, both because of their scale and because stolen funds are believed to support the country’s nuclear and ballistic missile programs. Groups such as Lazarus and APT38 have been linked to a long sequence of exchange hacks, DeFi exploits, and social‑engineering campaigns targeting engineers at crypto firms and other financial institutions. A recent report by TRM Labs estimates that North Korea stole about 577 million dollars in just two crypto hacks in early 2026, namely those targeting Drift Protocol and KelpDAO, accounting for roughly seventy‑six percent of all crypto hack losses in that period. Earlier analyses suggest that cumulative crypto thefts attributed to North Korean entities since 2017 amount to several billion dollars.
The methods used by these groups are diverse and increasingly sophisticated. Investigations and indictments have described campaigns in which North Korean IT workers obtained remote jobs at Western companies under false identities, then used their positions to gain access to internal systems and funnel revenue in crypto back to the regime. Others have involved “fake job offer” phishing lures sent to developers, which, when opened, install malware granting long‑term access to corporate networks. Once inside, attackers surveil infrastructure for hot wallets, internal tools for signing withdrawals, and possible misconfigurations in multisignature schemes. The U.S. Department of Justice has pursued multiple civil forfeiture actions against crypto assets linked to such heists, including a 2024 complaint targeting funds associated with approximately 879 million dollars in thefts by North Korean military hacking groups, as well as a separate action to seize over 7.7 million dollars allegedly laundered by North Korean IT workers. These enforcement efforts highlight both the scale of the threat and the growing willingness of authorities to track and seize tainted crypto.
Cybercrime Forums and Underground Markets
While state actors attract headlines, most crypto hacking is carried out by non‑state groups that operate within sprawling cybercrime ecosystems. Online forums and marketplaces provide venues where stolen data, exploit kits, and hacking services can be bought and sold. Europol recently announced the takedown of two of the world’s largest cybercrime forums, Cracked and Nulled, which together hosted more than ten million user accounts and served as “quick entry points” for aspiring cybercriminals. In that operation, authorities arrested two suspects and seized seventeen servers across several countries, disrupting infrastructure used for trading stolen credentials, malware, and operational tutorials. Although such forums are not exclusively focused on crypto, the credentials and tools available there often provide a foothold into exchanges, wallet providers, and cloud platforms used by crypto companies.
BreachForums, another notorious platform, has played a similar role in the sale and public leaking of stolen corporate data, including datasets that could be used to target crypto businesses. The site has been intermittently active; it was seized by law enforcement, revived under new management, and seized again in 2024, with the FBI later taking control of its servers as part of a larger operation. Reporting indicates that, even after the main domains were taken over, related dark‑web leak sites continued to threaten the release of stolen Salesforce data, prompting security experts to warn chief security officers that they had a short window to strengthen monitoring, audit configurations, and rehearse incident‑response plans. These episodes illustrate how the compromise of general SaaS platforms can cascade into crypto risks, given that many exchanges and DeFi teams rely on the same customer‑relationship and communication tools as other tech companies.
Teen Crews and Opportunistic Hackers
Not all crypto hacking is the work of elite coders or state‑backed units. Law enforcement has uncovered surprisingly young perpetrators behind some significant thefts, highlighting how accessible hacking has become thanks to widely shared tools and tutorials. In Paraguay, for example, police dismantled what they described as a teen hacking gang that stole around one million dollars and allegedly laundered part of the proceeds through cryptocurrency. Officers confiscated about 400,000 dollars’ worth of digital assets and reported that the gang used a mix of cash, cards, and crypto to obscure the origin of their funds. The suspects are said to have relied heavily on existing malware and social‑engineering scripts rather than novel exploits, underscoring that technical barriers to entry can be relatively low.
Such cases are not isolated. Our newsroom has covered multiple incidents of “script kiddies” leveraging off‑the‑shelf tools to compromise weakly protected servers, Wi‑Fi networks, or social media accounts, then turning to crypto as a way to monetize access. The combination of pseudonymous addresses and the perception—often mistaken—that law enforcement cannot track on‑chain activity can make younger attackers overconfident. Yet prosecutions, extraditions, and high‑profile sentencing decisions, including multi‑year prison terms for participants in major crypto heists, demonstrate that legal consequences can be severe. The challenge for policymakers is to deter entry‑level offenders without discouraging legitimate security research or contributing to a chilling effect on open‑source development.
Security Researchers, “Gray Hats,” and Responsible Disclosure
Alongside malicious actors, the crypto ecosystem depends on a community of security researchers who use hacking techniques to find and responsibly disclose vulnerabilities. These individuals and teams operate somewhere along a spectrum from strictly “white hat” behavior—reporting bugs to projects and sometimes even helping to remediate them—to more ambiguous “gray hat” actions, such as exploiting a vulnerability to prevent others from doing so and then negotiating the return of funds. High‑profile researchers have uncovered systemic flaws in major DeFi protocols, sometimes preventing nine‑figure losses by alerting developers before adversaries could strike, and in other cases recovering funds after a bug had been exploited but before the attacker had fully laundered them.
Our newsroom has reported on investigations by researchers like Paradigm’s Samczsun, who has mapped out broader hacking arsenals attributed to North Korea beyond the well‑known Lazarus group, revealing multiple advanced threat clusters and toolchains. Such work illustrates how defensive hacking—reverse‑engineering malware, tracing on‑chain flows, and probing DeFi contracts—can provide critical intelligence to projects and law enforcement alike. However, these activities also raise complex questions about liability and ethics: when does probing a live contract cross the line into unauthorized access, and under what conditions should “white hats” be compensated for their findings? Bug bounty platforms, coordinated vulnerability disclosure frameworks, and a culture of transparency are emerging as key ingredients in balancing innovation with safety.

The U.S. Department of Justice filed a civil forfeiture complaint in the U.S. District Court for the District of Columbia to seize over $7.74 million in cryptocurrency allegedly laundered by North Korean IT workers, led by indicted official Sim Hyon Sop, to evade U.S. sanctions and fund North Korea’s weapons program.

- 01North Korea attribution beyond Lazarus↗
Samczsun's disclosure that multiple advanced DPRK threat groups operate beyond the well-known Lazarus brand reframed the threat as a state program, not a single crew — making the scale feel newly alarming.
- 02DOJ forfeiture of stolen crypto↗
Civil forfeiture actions against hundreds of millions in Lazarus and APT38 proceeds gave readers a concrete answer to 'does stolen crypto ever get recovered' — a question every DeFi user has.
- 03First smart contract criminal conviction↗
Shakeeb Ahmed's three-year sentence was the first time 'I found an exploit' was treated as a crime rather than a bug bounty, directly changing how the industry thinks about white-hat lines.
- 04Cybercrime forum law enforcement busts↗
Takedowns of Cracked, Nulled, and BreachForums — platforms with tens of millions of users — showed readers that the supply chain enabling crypto-targeted attacks was being disrupted at the infrastructure level.
- 05AI autonomous exploit generation↗
Academic evidence that LLMs can generate working exploits against known vulnerabilities shifted AI hacking from theoretical to imminent, a threshold moment readers recognized immediately.
- 06X account hijacking for meme coin rugs
A single operator stealing $500K by phishing 15+ verified X accounts and launching rug pulls illustrated how social-layer attacks had become as profitable as on-chain exploits.
Techniques and Vectors: How Crypto Hacks Work
Crypto hacking techniques range from the mundane to the mathematically sophisticated. Many attacks exploit familiar weaknesses in human behavior, such as clicking on phishing links or reusing passwords; others target novel combinations of smart contract logic, off‑chain oracles, and cross‑chain messaging protocols. Increasingly, AI systems are being used on both sides of this contest: attackers deploy automated bots to scan contracts and craft phishing messages, while defenders use machine learning to detect anomalies in transaction flows and contract behavior.
While it is impossible to catalog every method in a single explainer, several categories of attack recur across major incidents. These include smart contract vulnerabilities, key theft and endpoint compromise, social engineering and fake apps, infrastructure failures in exchanges and bridges, AI‑assisted exploit development, and, on the horizon, quantum attacks on underlying cryptography. Each has distinct technical and organizational countermeasures, some of which are already well established and others still subjects of active research.
Smart Contract Vulnerabilities and On‑Chain Exploits
Smart contracts are programs deployed to blockchains that execute deterministically when called, without direct human intervention. Once deployed, they are usually difficult or impossible to change, which means that any bug can become a permanent part of the protocol’s behavior. Security research has identified a number of recurring vulnerability patterns in such contracts. One classic example is the reentrancy bug, where a contract sends funds to an external address before fully updating its own internal state; if the recipient is a malicious contract, it can call back into the original function repeatedly, draining funds before the balance is properly updated. Mitigations involve changing the order of operations so that state is updated before external calls, and using standardized patterns like OpenZeppelin’s ReentrancyGuard to prevent nested invocations.
Another common category is arithmetic overflow and underflow, where calculations on token balances or counters wrap around due to limitations in numeric types. In earlier versions of Solidity, the main language for Ethereum smart contracts, this could lead to situations where subtracting from a balance yielded a huge positive number, corrupting contract state and enabling theft. Modern compiler versions include built‑in checks that revert transactions on overflow or underflow, and libraries such as SafeMath provide explicit safeguards for arithmetic operations. Nonetheless, older contracts or those using custom math routines can still harbor these issues, especially when combined with complex loops and iterative logic that interact with gas limits.
Access control weaknesses are another pervasive problem. Contracts often include administrative functions for pausing operations, updating parameters, or performing emergency withdrawals. If these functions are not properly restricted—due to missing modifiers, misconfigured role‑based access control, or vulnerabilities in initialization routines—an attacker may be able to call them and seize control of the protocol. Mitigations involve using well‑tested patterns like Ownable or role‑based access control, ensuring that initialization functions can only be called once by authorized entities, and rigorously testing upgrade paths. When such controls are linked to off‑chain multisignature wallets, as in the Drift and Bybit cases, the security of those multisigs becomes a critical part of the overall threat model.
A further class of vulnerabilities revolves around incorrect assumptions about time, randomness, and external data. Contracts that depend on block timestamps or block numbers for critical decisions can be manipulated by miners or validators within certain bounds, enabling subtle timing attacks. Those that rely on insecure sources of randomness, such as hashing predictable values or using future block hashes, may be vulnerable to manipulation in games, lotteries, or NFT mints. Oracles, which feed external prices and events into smart contracts, can also be attacked, either by manipulating the underlying data sources or by exploiting the way protocols aggregate and trust oracle inputs. Front‑running and miner‑extractable value (MEV) add another dimension: if attackers can see pending transactions and insert their own with higher fees, they can sandwich or reorder user trades to their advantage. Defenses include using verifiable random functions, robust oracle designs like Chainlink’s, commit‑and‑reveal schemes for sensitive actions, and transaction bundling to reduce per‑transaction observability.
Key Theft, Wallet Drains, and Endpoint Compromise
Despite their technical sophistication, blockchains ultimately rely on the secrecy of private keys. If an attacker obtains the private key controlling a wallet, they can sign any transaction, and the network will treat it as authorized by the legitimate owner. As a result, many “crypto hacks” are, at root, traditional endpoint compromises. Malware installed on a user’s device can search for wallet files, screenshots of seed phrases, or clipboard contents, exfiltrating them to remote servers. Phishing sites that convincingly mimic wallet interfaces can prompt users to enter seed phrases or sign malicious transactions. SIM‑swap attacks, where an attacker convinces a telecom provider to transfer a victim’s phone number to a new SIM card, allow interception of SMS‑based two‑factor authentication codes, which can then be used to reset exchange account passwords.
General cybersecurity guidance remains highly relevant here. Security experts emphasize the importance of keeping software and operating systems up to date, as attackers constantly probe for known vulnerabilities that have not been patched. Using unique, strong passwords for different accounts minimizes the damage if one credential is compromised; password managers can help users adopt such practices without needing to memorize dozens of complex strings. Two‑factor authentication, preferably using hardware security keys or app‑based codes rather than SMS alone, adds an extra layer of assurance that the person logging in is the legitimate account holder. For crypto specifically, hardware wallets that store private keys in secure enclaves and require physical confirmation of transactions can significantly reduce the risk that malware on a connected computer can silently authorize transfers.
Endpoint security also encompasses network devices and “smart” hardware. Routers and Internet‑of‑Things devices often ship with default usernames and passwords that can be trivially guessed if not changed, allowing attackers to pivot into local networks and monitor or tamper with traffic. Public Wi‑Fi networks pose additional risks of interception or spoofing. Using virtual private networks (VPNs) can help mitigate some of these threats by encrypting traffic, though they are not a panacea. Ultimately, for any device used to manage substantial crypto holdings, a conservative approach—minimal installed software, restricted browsing, and careful control over physical access—remains best practice.
Social Engineering, Phishing, and Fake Apps
A large proportion of successful hacks exploit human psychology rather than technical flaws. Phishing emails that appear to come from trusted sources, such as exchanges, wallet providers, or even internal company departments, can trick users into clicking malicious links or downloading harmful attachments. These links may lead to spoofed websites that look almost identical to legitimate login or wallet pages but are under attacker control. Once users enter their credentials or seed phrases, the attackers immediately use them to seize accounts or drain funds. General advice to “avoid clicking on strange links,” “look for HTTPS,” and “download software only from first‑party sources” may sound simplistic, but it reflects patterns seen repeatedly in real‑world incidents.
In recent months, our newsroom has documented scams where attackers hacked the social media accounts of high‑profile crypto personalities and used those accounts to promote fraudulent token launches. Followers, trusting the familiar handle and profile picture, clicked through to mint pages that were, in reality, carefully crafted to steal approvals or redirect payments to the attacker’s address. Even technically savvy users can be caught off guard when a trusted figure suddenly announces an “exclusive” opportunity available for a short time. Phishing has also targeted corporate staff; by compromising a single employee’s email or messaging account at a wallet or exchange provider, attackers can pivot into internal systems, create fake support tickets, or push malicious updates to users. Security training that teaches staff and users to recognize the telltale signs of phishing, coupled with enforced technical controls like domain‑based message authentication and strict app‑store policies, is therefore a crucial part of any defense strategy.
Exchanges, Bridges, and Infrastructure Exploits
Beyond end‑user devices and contracts, the connective tissue of the crypto ecosystem—exchanges, custodians, and bridges—presents powerful choke points for attackers. Centralized exchanges manage large hot wallets and complex trading infrastructure, making them attractive targets. Vulnerabilities can arise from misconfigured cloud services, outdated internal tools, or insufficient segregation of duties among staff. DeFi bridges, which allow assets to move between blockchains, are particularly complex; they often combine on‑chain light clients, off‑chain relayers, and multisignature schemes. A bug in any component, or a compromise of key holders, can allow an attacker to mint “backed” assets without depositing corresponding collateral, effectively creating counterfeit tokens that can be sold into the market.
The importance of secure multisignature design is highlighted by incidents like the Drift Protocol hack, where the core issue appears to have been a breach of the multisig mechanism rather than a bug in business logic. In practice, this could result from phishing or compromising the devices of multiple signers, finding flaws in wallet software, or exploiting overly permissive access policies. Bridges have also been singled out by both security experts and traditional finance executives as the “weakest link” in DeFi’s security stack, given their centrality and complexity. At industry events, executives from major audit firms and banks have warned that they do not expect sustained institutional growth in DeFi until bridge security is significantly improved, with some arguing that the entire multi‑layer stack—smart contracts, key management, monitoring, and governance—must be upgraded.
Infrastructure risks extend beyond crypto‑native platforms to the general SaaS tools that many projects rely on. A prominent example involves the compromise of Salesforce data, where attackers exfiltrated records and then used platforms like BreachForums to threaten leaks unless ransoms were paid. Security experts pointed out that “SaaS is the new blast radius,” noting that interconnected services often trust each other via OAuth and app‑to‑app permissions that can be abused. Recommended countermeasures include turning on OAuth app governance, enforcing least‑privilege scopes, limiting token lifetimes, implementing automated revocation when anomalies are detected, rotating keys and tokens regularly, shortening session durations, and requiring step‑up authentication for high‑risk actions. For crypto companies, which may integrate wallets, analytics, customer‑support platforms, and marketing tools into a single operational environment, hardening this SaaS layer is as important as securing on‑chain contracts.
AI‑Powered Attacks and Automated Exploit Bots
Artificial intelligence is rapidly transforming the threat landscape. AI agents and bots can now autonomously scan smart contract repositories, identify likely vulnerability patterns, and even generate proof‑of‑concept exploits. Reporting has described AI bots as self‑learning software that not only automates attacks but also continuously refines them based on observed defenses, making them more dangerous than traditional, static hacking methods. In one widely watched case, a crypto token lost around half of its value in a short period following an AI‑assisted exploit, prompting market observers to warn that AI‑driven hacking could dramatically increase the speed and scale of attacks on DeFi. Founders who once worried mainly about human adversaries are now sounding alarms about an emerging generation of “superhuman” coding agents that can relentlessly test every edge case in protocol logic.
Industry security leaders have gone so far as to say that, given current AI capabilities, they now consider “all” of DeFi unsafe, at least in the sense that any non‑trivial protocol might harbor undiscovered, exploitable bugs that AI systems are likely to find sooner rather than later. These concerns are not theoretical. Large language models can already write and refactor Solidity contracts, create fuzzing harnesses, and suggest changes to bypass code‑review checks. Attackers can use generative models to craft highly targeted phishing emails in multiple languages, clone voices and faces for social‑engineering calls, and automatically generate malicious websites that mimic legitimate ones. At the same time, defenders are exploring AI‑based tools that scan codebases for known vulnerability patterns, monitor on‑chain activity for anomalous flows, and simulate attacks in testing environments before deployment. Whether AI ultimately tilts the balance toward attackers or defenders remains an open question, but in the short term, it clearly amplifies the capabilities of both.
Quantum Threats and Cryptographic Foundations
Looking further ahead, advances in quantum computing may pose systemic risks to the cryptographic primitives underlying most blockchains. Many cryptocurrencies rely on elliptic curve digital signature algorithms (ECDSA) to secure private keys and authorize transactions. A recent whitepaper from Google researchers argues that, contrary to earlier optimistic assumptions, future quantum computers may be able to break widely used elliptic curve schemes with fewer physical qubits and shorter runtimes than previously estimated. If such capabilities become practical, an adversary with a sufficiently powerful quantum computer could, in principle, derive private keys from public keys for addresses that have exposed their public keys on‑chain, allowing them to sign transactions and spend funds.
This scenario is particularly concerning for large, dormant holdings, such as the approximately 2.3 million bitcoins attributed to Satoshi Nakamoto’s early mining activity. A recent discussion on the Bankless podcast, summarized by Phemex, explored strategies for addressing the quantum risk posed to such coins. Proposals included preemptively burning the coins, implementing hourglass mechanisms that would automatically lock or redistribute them, or creating pegged sidechains with post‑quantum cryptography where vulnerable addresses could be migrated. Binance’s former CEO has suggested that, if these coins remain inactive, it might be prudent to lock or burn the associated addresses to prevent a future quantum‑enabled theft. Google’s researchers, for their part, recommend that the broader cryptocurrency community begin transitioning to post‑quantum cryptography (PQC), avoid reusing addresses to limit exposure of public keys, and consider policy options for dealing with abandoned or unresponsive wallets. While practical quantum attacks are not imminent, planning for such a migration is a non‑trivial research and governance challenge.
Defending Against Crypto Hacking
Against this backdrop of evolving threats, defense in the crypto space must be multi‑layered, combining individual security hygiene, rigorous protocol engineering, robust operational practices, law‑enforcement cooperation, and ongoing research. No single control can eliminate risk, but a thoughtful combination of measures can dramatically reduce the likelihood and impact of successful attacks.
Defenses can be organized along several dimensions: user‑level practices that safeguard keys and accounts; development and deployment methodologies that minimize vulnerabilities in smart contracts and infrastructure; organizational controls that govern access to critical systems; and ecosystem‑level mechanisms, such as insurance funds and coordinated incident response, that help absorb and recover from inevitable failures. The rapidly changing nature of both AI and cryptographic research adds a further requirement: adaptability.
Security Hygiene for Individuals
For individual users, many of the most effective defenses are well‑established cybersecurity practices applied diligently to the crypto context. Keeping operating systems, browsers, and wallet software up to date closes off known vulnerabilities that attackers routinely scan for. Using strong, unique passwords for each exchange, email, and social media account prevents a compromise of one service from cascading to others; password managers simplify this otherwise daunting task. Enabling two‑factor authentication, preferably via hardware security keys or time‑based one‑time password apps, adds a robust second layer to account logins, making it much harder for attackers to gain access even if they obtain a password.
Users should be skeptical of unsolicited messages, unexpected links, and urgent calls to action, especially when they involve moving funds or revealing sensitive information. Verifying URLs, bookmarking official sites, and manually typing addresses rather than following email links can help avoid spoofed websites. Only downloading wallet and trading apps from official stores or directly from verified project websites reduces the risk of installing malicious clones. For those holding significant amounts of crypto, using hardware wallets in combination with an air‑gapped or minimally used computer can greatly reduce exposure to malware. Changing default router credentials, segmenting home networks where possible, and being cautious about public Wi‑Fi usage further enhance the security of the environment in which wallets operate.
Protocol and Smart Contract Security Practices
For developers and protocol teams, smart contract security begins long before deployment. Threat modeling—systematically identifying potential adversaries, their capabilities, and the assets at risk—should inform architectural decisions from the outset. Using established, audited libraries for common tasks, such as token standards and access control, reduces the chance of introducing subtle bugs. Formal verification, where feasible, can mathematically prove that certain properties hold under all possible execution paths, offering stronger guarantees than traditional testing. Comprehensive test suites, including unit tests, integration tests, and property‑based fuzzing, help uncover edge cases that might otherwise be missed.
Security research has identified numerous best practices for mitigating specific categories of vulnerabilities. Reentrancy risks can be reduced by updating contract state before making external calls and by using guard mechanisms that prevent reentrant execution. Arithmetic errors can be avoided by compiling with modern Solidity versions that enforce checks and by relying on battle‑tested math libraries. Access control should be implemented with clear, minimal roles, avoiding overly powerful “god modes” tied to single keys; multisignature schemes and time‑locked operations can provide additional safety, especially for high‑impact changes. Contracts that depend on external data or randomness should use robust oracle frameworks and verifiable random functions, avoiding naive constructions that miners or validators can manipulate.
Front‑running and MEV exploitation can be mitigated through techniques like slippage limits, commit‑and‑reveal schemes, and batched auctions, which reduce the ability of attackers to target individual trades. Developers must also be mindful of gas usage and looping constructs, ensuring that contracts cannot be easily “griefed” into reverting through denial‑of‑service patterns or excessive gas consumption. Crucially, no audit or formal method provides absolute security. Protocols should plan for failure by implementing circuit breakers, pausable contracts, and emergency response procedures, as well as by maintaining insurance funds or coverage arrangements where feasible.
Operational Security for Teams and Infrastructure Providers
Even perfectly coded contracts can be compromised if the surrounding operational environment is weak. Key management is central: administrative keys controlling upgrades, parameter changes, or treasury movements should be stored in hardware wallets, distributed across multiple signers, and protected by strict policies on device usage and physical access. Teams should adopt least‑privilege principles for internal systems, ensuring that no single employee or machine has more access than is necessary for their role. Regular security training, phishing simulations, and clear reporting channels for suspicious activity can help staff resist social‑engineering attempts.
Given the reliance on third‑party SaaS tools, crypto organizations must also harden their broader application ecosystem. Lessons from the BreachForums and Salesforce incidents underscore the importance of managing OAuth integrations, scoping permissions carefully, limiting token lifetimes, and automating revocation when anomalies are detected. Security teams should conduct regular audits of app‑to‑app trust relationships, rotate API keys and secrets, and enforce multi‑factor authentication for access to sensitive dashboards and admin panels. Incident‑response playbooks, including clear communication plans for users and partners, should be rehearsed so that teams can act quickly when a breach is detected.
Monitoring and observability are vital. On‑chain analytics can detect unusual patterns of withdrawals, sudden changes in contract ownership, or unexpected large transactions through bridges. Off‑chain logs from servers, build systems, and CI/CD pipelines can reveal indicators of compromise. Increasingly, firms are deploying AI‑powered anomaly detection systems to sift through this data and raise alerts for human review. While such tools are not a substitute for solid foundational practices, they can provide early warning signals that shorten the window between intrusion and response.
Law Enforcement, Regulation, and the Deterrence Landscape
Contrary to the perception that crypto is a lawless frontier, law‑enforcement agencies around the world have become increasingly adept at tracing and seizing illicit digital assets. The takedown of major cybercrime forums like Cracked and Nulled, with their ten million users and seventeen servers, demonstrates that even large underground marketplaces can be disrupted through coordinated international action. The repeated seizures of BreachForums domains and infrastructure by U.S. and allied authorities, alongside arrests of administrators, send a similar message. While such operations cannot eliminate cybercrime, they raise the cost of operating at scale and reduce the availability of ready‑made tools and data for would‑be attackers.
Crypto‑specific enforcement has also intensified. Civil forfeiture complaints targeting hundreds of millions of dollars in coins linked to North Korean heists show how on‑chain tracing, exchange cooperation, and court orders can be combined to claw back a portion of stolen funds. Extradition cases, like that of the Saskatchewan man accused of university supercomputer hacking for crypto mining, highlight that cross‑border jurisdictional barriers are not insurmountable. Police actions against teen gangs in Paraguay and sentences of many years in prison for individuals involved in large crypto thefts reinforce the message that criminal activity in this space carries significant legal risk. In parallel, regulatory frameworks for exchanges, custodians, and stablecoin issuers are tightening, with security and incident disclosure requirements increasingly codified.
Risk Management for Investors and Users
For investors and everyday users, the practical question is how to assess and manage hacking risk when choosing where to deploy capital. Technical audits, bug bounty programs, and the reputations of developer teams all provide useful signals, but none guarantees safety. Users should pay attention to how protocols handle governance and upgrades, what mechanisms exist for emergency shutdown or fund recovery, and how transparent teams are about past incidents and mitigations. DeFi bridges and high‑yield schemes warrant particular scrutiny, given their history of exploits and structural complexity.
The reluctance of large banks and institutional players to fully embrace DeFi, as voiced by executives who argue that growth will remain constrained until the hacking problem is significantly mitigated, offers a somewhat counterintuitive protective insight for retail users. If a protocol is not yet trusted by conservative institutions, its risk profile is likely still evolving. On the other hand, the surge in demand for secure hardware wallets and custodial services, evidenced by expansion plans and potential public listings from major security firms, reflects a growing recognition that professional‑grade key management and custody are essential for larger holdings. Our newsroom has reported on companies like Ledger enjoying record years as more investors seek protection from hacking, suggesting that security infrastructure is itself becoming a core pillar of the maturing crypto market.

Israeli spyware firm NSO hit with $167 million judgment for hacking 1,400 WhatsApp users, setting a major legal precedent.

Shakeeb Ahmed sentenced — first smart contract hacking conviction
FBI seizes BreachForums hacking forum and its servers
- 2024-07regulatory
FBI charges four FIN9 members in $71M crypto hacking case
Europol dismantles Cracked and Nulled forums; 17 servers seized
- 2025-05regulatory
NSO Group hit with $167M judgment for WhatsApp spyware campaign
North Korea steals majority of all crypto hack value in just two attacks
DOJ files civil forfeiture for $7.74M laundered by North Korean IT workers
Research Frontiers: Building a Safer Crypto Ecosystem
The defense against hacking in crypto is not static. It is animated by ongoing research in secure programming languages, formal verification, cryptographic protocols, AI‑driven security analytics, and policy frameworks for quantum transition. These efforts aim not only to patch individual vulnerabilities but to fundamentally reshape the security properties of decentralized systems.
Research communities straddle academia, industry, and open‑source projects. On one side, large tech firms and universities explore new cryptographic schemes and verification methods; on the other, specialized Web3 security teams scrutinize live contracts and design practical mitigation patterns. Collaboration between these worlds is critical: academic breakthroughs must be translated into deployable libraries and standards, while real‑world exploit data can inform theoretical models of attacker behavior.
Formal Verification, Safer Languages, and Secure Tooling
One promising direction is the use of formal methods to prove that smart contracts satisfy specified properties, such as the invariance of total token supply or the impossibility of unauthorized withdrawals. While complete verification of complex DeFi systems remains challenging, targeted proofs for critical components, combined with exhaustive testing for the rest, can substantially reduce risk. Languages such as Move and domain‑specific subsets of Solidity are being designed with stronger static guarantees, making certain classes of bugs structurally harder to introduce. Tools that automate symbolic execution, model checking, and property‑based testing are increasingly integrated into DeFi development workflows.
Secure tooling also encompasses compilers and build systems. Ensuring that compilers do not introduce subtle miscompilations, that source code matches deployed bytecode, and that build pipelines are protected against tampering are all areas of active concern. The use of reproducible builds and open‑source verification tools can help communities independently confirm that widely used protocols deploy exactly the code they claim to. Over time, one can imagine a shift from ad hoc audits toward more rigorous, standardized certification processes, akin to those used in safety‑critical industries, although balancing speed of innovation with such rigor remains a perennial tension.
On‑Chain Analytics and Attribution Research
Another research frontier lies in on‑chain analytics and attribution, which seek to map the behavior of hacking groups, trace stolen funds, and identify infrastructure used for laundering. Firms like TRM Labs and Chainalysis have built extensive datasets linking blockchain addresses to particular entities or clusters based on transaction patterns, exchange interactions, and off‑chain intelligence. Their work on North Korean operations, for instance, has revealed characteristic flows through specific mixers, OTC brokers, and bridge services, helping exchanges and enforcement agencies detect and freeze funds earlier in the laundering chain.
Academic researchers and independent analysts contribute by developing new heuristics for identifying mixer usage, cross‑chain swap patterns, and changes in tactics over time. Combined with machine learning, these approaches can flag emerging threats and track the evolution of known groups. There is an inherent cat‑and‑mouse dynamic: as attribution improves, attackers adopt more sophisticated obfuscation techniques, use privacy‑enhancing technologies, or attempt to fragment their activities across many smaller operations. Nevertheless, the growing body of research suggests that, contrary to some perceptions, crypto is often easier to trace than cash, especially when large sums are involved.
AI for Defense as Well as Offense
While much attention has focused on AI’s role in enhancing attacks, it also offers powerful tools for defense. Machine‑learning models can analyze codebases to detect patterns associated with known vulnerabilities, prioritize contracts for human review, and suggest remediation strategies. On‑chain anomaly detection systems can monitor transaction flows in real time, flagging unusual activity such as rapid, large withdrawals from a protocol, atypical usage of admin functions, or sudden spikes in cross‑chain bridge usage. Natural‑language processing tools can help parse semi‑structured disclosures, forum posts, and commit messages for early signs of emerging threats.
However, AI‑driven defense is not a silver bullet. Models can generate false positives that overwhelm analysts or false negatives that miss subtle manipulations. Attackers can attempt to poison training data or craft adversarial inputs designed to bypass detection. Human expertise remains essential for interpreting model outputs, refining detection rules, and making judgment calls about when to trigger emergency responses, such as pausing a protocol. The most effective strategies are likely to involve close collaboration between AI systems and human security teams, with feedback loops that allow both to improve over time.
Quantum‑Safe Cryptography and Migration Planning
The looming quantum threat adds another layer of complexity to crypto’s security roadmap. As noted earlier, research by Google and others has highlighted the potential for future quantum computers to break elliptic curve cryptography more efficiently than once believed, raising concerns about the long‑term safety of existing blockchains. In response, the cryptography community has been developing post‑quantum algorithms—such as lattice‑based, code‑based, and multivariate schemes—that are believed to resist quantum attacks. Standardization efforts are underway through bodies like NIST, and some experimental blockchains already incorporate PQC in various forms.
For established networks like Bitcoin and Ethereum, migration is more challenging. Proposals include introducing new address types that use post‑quantum signatures, encouraging users to move funds from legacy addresses to quantum‑safe ones, and creating mechanisms for reclaiming or repurposing long‑dormant coins that may be vulnerable if their public keys have been exposed. The debate over how to handle Satoshi’s 2.3 million bitcoins encapsulates both technical and philosophical questions: should the community proactively alter the status of historically important coins to reduce systemic risk, or would such interventions undermine property rights and the ethos of immutability? Regardless of how such debates are resolved, the need to plan for quantum‑safe transitions is becoming increasingly clear.
Conclusion
Hacking in the crypto ecosystem is not a single phenomenon but a constellation of threats that span technical bugs, human fallibility, organizational weaknesses, and emerging capabilities in AI and quantum computing. From reentrancy attacks on DeFi protocols to phishing campaigns that hijack social media accounts, from North Korean state‑backed heists to teenage gangs experimenting with off‑the‑shelf tools, the spectrum of adversaries and methods is broad. The core challenge arises from crypto’s defining strengths: permissionless access, open‑source development, and irreversible, global settlement. These properties make innovation fast and censorship difficult, but they also magnify the consequences of error or malice.
The industry’s response has been mixed but increasingly mature. On one hand, the persistence of bridge exploits, multisignature misconfigurations, and SaaS‑layer breaches has prompted prominent voices to argue that DeFi cannot achieve mainstream adoption without a step change in security. On the other, falling aggregate hack volumes, more aggressive law‑enforcement actions, and the growth of a specialized security sector—encompassing auditors, hardware wallet manufacturers, and analytics firms—indicate that defenses are evolving. Research into formal verification, AI‑assisted code analysis, and post‑quantum cryptography offers hope that future protocols can be substantially more robust than the first generation. Yet no technology can fully compensate for weak governance, poor operational practices, or user inattention.
For participants in the crypto economy—whether individual investors, developers, or institutions—the practical implication is clear. Security cannot be an afterthought or a compliance checkbox; it must be a core design and investment consideration. Users should adopt basic digital hygiene and hardware‑based key storage, developers must treat audits and threat modeling as non‑negotiable, and organizations need to harden their SaaS and cloud environments as vigorously as their on‑chain components. At the ecosystem level, transparency about incidents, support for responsible disclosure, and collaboration with law enforcement will be crucial in deterring attacks and mitigating their impact. Hacking will never disappear, but its influence on crypto’s trajectory can be managed.
North Korea's multiple DPRK hacking groups — Lazarus, APT38, and others — stole 76% of all crypto hack value in 2026 across just two major attacks, representing a persistent, state-funded adversary with no off switch.
Logic flaws in smart contracts remain the primary on-chain attack vector; the Shakeeb Ahmed conviction confirmed prosecutors now treat deliberate exploitation as felony computer fraud, but deterrence lags the attack surface.
Large language models have demonstrated the ability to generate working exploits against known CVEs in academic settings, with at least one token suffering a 50% crash attributed to an AI-assisted attack vector.
- Social engineering and phishingMedium
Compromising high-follower social media accounts to launch meme coin rug pulls has become a repeatable, low-cost attack pattern generating hundreds of thousands of dollars per campaign with minimal technical skill required.
DOJ civil forfeiture actions against North Korean wallets and the first-ever smart contract criminal conviction signal a maturing enforcement posture, but cross-jurisdictional prosecution remains slow and recovery rates low.
Coordinated Europol and FBI takedowns of BreachForums, Cracked, and Nulled removed key marketplaces for stolen credentials and exploit tooling, but replacement forums emerge within months of each seizure.
Outlook
Looking ahead, the hacking landscape in crypto is likely to become more automated, more entangled with traditional IT risks, and more shaped by geopolitical dynamics. AI will continue to lower barriers for attackers and defenders alike, making the speed of response and the quality of tooling decisive factors. State actors, particularly in sanctioned regimes, are unlikely to abandon profitable crypto heists voluntarily, ensuring that the cat‑and‑mouse game of attribution and seizure will persist. At the same time, regulatory clarity, improved security standards, and the gradual integration of post‑quantum schemes should make the core infrastructure of leading blockchains progressively harder to compromise.
Whether DeFi can achieve its ambition of becoming a trusted, global alternative to some functions of traditional finance will hinge on its ability to substantially reduce hacks and communicate realistic risk profiles to users. If the sector succeeds in embedding robust security practices from design through operations, the narrative may shift from one of “wild west” experimentation to one of resilient, open financial rails. If not, repeated high‑profile breaches may continue to erode trust and keep many large institutions on the sidelines. In either case, understanding hacking—not just as a buzzword but as a concrete set of threats, incentives, and countermeasures—will remain essential for anyone serious about the future of crypto.
Latest Hacking news
Crypto security company Ledger plots $4bn New York listing. French group enjoys record year as more investors seek protection from hacking. It is working with bankers at Goldman Sachs, Jefferies and Barclays on the deal, which could take place as soon as this year, according to people familiar with the matter. They cautioned that plans could yet change.
The U.S. Department of Justice filed a civil forfeiture complaint in the U.S. District Court for the District of Columbia to seize over $7.74 million in cryptocurrency allegedly laundered by North Korean IT workers, led by indicted official Sim Hyon Sop, to evade U.S. sanctions and fund North Korea’s weapons program.
Israeli spyware firm NSO hit with $167 million judgment for hacking 1,400 WhatsApp users, setting a major legal precedent.
Paradigm’s Samczsun uncovers North Korea’s broader hacking arsenal beyond Lazarus, exposing multiple advanced threat groups and tactics.
Europol and German law enforcement dismantle Cracked and Nulled hacking forums with over 10 million users. Arrest two suspects and seize 17 servers in major cybercrime bust.
This scammer has stolen ~$500K over the past month by hacking 15+ X accounts with phishing emails and launching meme coin rug pulls with their accounts.Sources
- https://www.tradingview.com/news/cointelegraph:d4a6754ea094b:0-can-ai-bots-steal-your-crypto-the-rise-of-digital-thieves/
- https://www.bloomberg.com/news/articles/2026-06-14/crypto-token-s-50-wipeout-shows-magnitude-of-ai-hacking-threat
- https://www.instagram.com/p/DY1oKrjgXbc/
- https://www.bakerdatacounsel.com/blogs/deeper-dive-understanding-the-2023-24-crypto-threat-landscape/
- https://www.instagram.com/reel/DYdjZmPDESl/
- https://www.justice.gov/opa/pr/department-files-civil-forfeiture-complaint-against-over-774m-laundered-behalf-north-korean
- https://www.facebook.com/BitPinas/posts/-the-drift-protocol-hack-experienced-an-identical-method-to-the-bybit-hack-from-/1414777493995460/
- https://www.moomoo.com/news/post/70989454/defi-won-t-win-over-big-banks-until-it-fixes
- https://www.cbc.ca/news/canada/saskatchewan/ryan-james-roach-saskatoon-ordered-for-extradition-to-us-from-canada-crypto-mining-hacking-9.7224246
- https://www.europol.europa.eu/media-press/newsroom/news/law-enforcement-takes-down-two-largest-cybercrime-forums-in-world
- https://phemex.com/news/article/debate-over-handling-satoshis-23-million-bitcoins-amid-quantum-threats-73623
- https://www.trmlabs.com/resources/blog/north-korea-stole-76-of-all-crypto-hack-value-in-2026-with-just-two-attacks?scLang=en
- https://en.wikipedia.org/wiki/BreachForums
- https://www.dlnews.com/articles/regulation/paraguay-police-confiscate-crypto-from-teen-hacking-gang/
- https://www.offshorealert.com/usa-v-bitcoin-et-al-forfeiture-complaint-north-korean-crypto-theft/
- https://www.csoonline.com/article/4071014/fbi-seizes-breachforums-servers-as-threatened-salesforce-data-release-deadline-approaches.html
- https://www.chainalysis.com/blog/crypto-hacking-stolen-funds-2025/
- https://www.cobalt.io/blog/smart-contract-security-risks
- https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/
- https://www.fortinet.com/resources/cyberglossary/what-is-hacking
Community notes
Spot something off or out of date? Drop a note. Editors review topic notes daily and roll accepted fixes into the explainer — contributors are recognized in the monthly $SQUID drop.
Loading notes…
