Hackers tied to North Korea stole roughly $6.36 billion from Binance on Wednesday, stripping the world's largest cryptocurrency exchange of funds across ten blockchains in a heist that blockchain intelligence firms are calling the largest crypto theft in history.
The attack, which began at 8:05 p.m. UTC on October 29, moved faster than most exchange security teams could respond. The bulk of the money was gone within 20 minutes.
Binance suspended deposits and withdrawals shortly after detecting the breach and said user funds would be covered in full. "Investigating a potential security issue," the exchange wrote in an early-evening post, adding that user assets were safe. By late that night, a coalition of blockchain infrastructure firms had frozen roughly $3 billion of the stolen assets, though more than $2.4 billion remained in the attacker's control as of press time.
How They Got In
Blockchain intelligence firm TRM Labs, which traced the attack in near real-time, said the intrusion bore the hallmarks of TraderTraitor, the North Korean state-sponsored hacking unit that the FBI also attributed to February's $1.5 billion Bybit breach.
The preparation started at least 36 hours before the theft. TRM Labs found that the attackers funded an operator wallet with small withdrawals from Tornado Cash, a crypto mixing service, then ran test transactions across wallets they controlled. In the day before the main theft, the attackers rehearsed the final version of their code on a third wallet before installing it on a live Binance hot wallet.
The technical method on Ethereum was particularly precise. The attackers used EIP-7702, an account delegation feature introduced in a recent Ethereum upgrade, to effectively convert a Binance hot wallet into a sweeper they controlled. A single transaction carried 50 pre-signed authorizations; one matched the wallet's transaction count exactly, granting the attackers the ability to sweep new incoming deposits for hours after the initial theft, all the way until 11:56 p.m. UTC.
On nine other blockchains, including Bitcoin, Tron, XRP Ledger, Solana, Arbitrum, and several Ethereum layer-2 networks, wallets sent funds through standard signed transfers during the same window. TRM's analysis concluded the most likely explanation was that the attacker had somehow obtained the ability to instruct Binance's hot wallet signing infrastructure to authorize transactions of their choosing. Binance has not yet published a root cause analysis.
What Was Taken
The breakdown by chain is staggering. Ethereum accounts for the largest slice: about $3.79 billion, including 200,630 ETH and roughly 1.875 billion USDT. Bitcoin follows with 18,270 BTC worth approximately $1.47 billion. Tron contributed about $628 million, primarily USDT, and XRP Ledger added 233 million XRP worth around $296 million. The remaining losses were spread across Solana, Arbitrum, Optimism, Base, Avalanche, and Polygon.
At those figures, the theft dwarfs every previous crypto hack on record by a considerable margin. The Bybit breach in February 2025, which itself broke every prior record, involved $1.5 billion. This attack is roughly four times larger.
The Freeze Race
Within hours of the theft, stablecoin issuers and blockchain governance bodies began freezing assets. Tether moved first, blacklisting 971 million USDT across wallets traced to the attacker at 9:01 p.m. UTC. Circle followed three minutes later with a freeze on $823 million in USDC, acting in coordination with law enforcement. Ripple froze 40.5 million RLUSD at 10:01 p.m. The Arbitrum Security Council executed forced transfers of 8,426 ETH and 74.6 million ARB tokens after midnight.
By 11:35 p.m. UTC, Binance said the verified total of frozen assets had reached $2.54 billion. TRM Labs placed the figure closer to $2.7 billion by 12:30 a.m. the following morning.
The attacker, however, moved quickly to convert portions of the stolen funds. Some USDT was swapped for ETH at a discount of more than 10%, and the attacker used Aave, a decentralized lending protocol, to borrow ETH against frozen stablecoin positions. As of the morning of October 30, the attacker still held more than 420,000 ETH and all 18,270 BTC, assets beyond the reach of any issuer's freeze function.
North Korea's Crypto Playbook
The FBI said it was aware of the incident and working with partners to assess the activity. The U.S. Secret Service had not responded to a request for comment at time of publication.
The timing fits a pattern that intelligence analysts have tracked closely. Chainalysis reported that North Korean operatives stole about $2 billion in cryptocurrency throughout 2025. TRM Labs found that two North Korea-linked groups accounted for three-quarters of all crypto hack losses in the first quarter of 2026 alone. The funds are widely believed to support Pyongyang's weapons programs, which have been cut off from conventional financial markets through international sanctions.
TRM Labs said it expects the attacker to route remaining funds through cross-chain bridges, swap services, and over-the-counter brokers in the coming weeks, and said it was monitoring those flows in real time.
A hacktivist group has published internal records identifying more than 41,000 Department of Homeland Security employees and contractors, in what security researchers are calling one of the most detailed government workforce exposures in recent memory.
The group, which calls itself the "Department of Peace," shared the data with Distributed Denial of Secrets (DDoSecrets), a nonprofit that publishes leaked government datasets, and with Swiss hacker-journalist maia arson crimew. The records went public on October 29 and cover staff across nine DHS agencies.
The group tied the release directly to DHS Secretary Markwayne Mullin's July 17 comments, in which he told reporters he was "turning up the heat" on immigration enforcement. That remark, the group said, was the trigger.
What the data contains
The leaked dataset holds 41,191 records spanning employees and contractors across nine DHS sub-agencies, pulled from nearly 7,000 offices and more than 2,200 locations. Each record contains names, job titles, supervisor relationships, direct reports, employment status, workplace addresses, email addresses, phone numbers, and internal group memberships.
CBP accounts for the largest share with 21,329 records, followed by ICE at 6,598 and USCIS at 6,245. Homeland Security Investigations holds 3,421 records, DHS headquarters 1,755, and CISA 980. The Federal Protective Service, FLETC, and the Science and Technology Directorate account for the remainder. Combined, the exposed records represent roughly one-fifth of DHS's reported headcount of 222,538, according to the DOGE website. CISA records were pulled from the public-facing search results but remain in the underlying dataset.
The Icepick tool
Crimew, who faces a U.S. federal indictment tied to prior leaks, built a searchable interface called "Icepick" and hosted it at icepi.cx. The domain registrar pulled the site down shortly after launch. DDoSecrets responded by releasing the tool's source code publicly. By Thursday morning, the searchable site was offline, but the data itself continued to circulate.
DDoSecrets co-founder Emma Best said the dataset extends well beyond contact information. The records, she wrote, identify officials overseeing covert and undercover operations, the government's internal effort to track down leakers, and the now-defunct BlueLeaks investigation. Crimew described it as "a complete game changer for anyone investigating DHS" and said it "provides FOIA material for years to come."
Ryan Shapiro of Property of the People, a government transparency organization, offered a narrower read, noting that staff contact information could prove useful for Freedom of Information Act requests.
Okta in the spotlight
The Department of Peace claimed the data came from an Okta single sign-on service used internally at DHS. Okta said it reviewed the report and found no evidence that its systems or data had been affected.
That denial has not fully closed the question. CyberScoop verified that numerous active CISA employees appear in the dataset alongside former agency leaders who left government years ago. The records also reference internal groups tied to COVID-19 planning and a 2023 internal summit, suggesting the data spans multiple years and may reflect sustained access rather than a single point-in-time pull.
Bluesky moved to block links pointing to the leaked data and flagged them as malicious, according to WIRED. The speed with which journalists and researchers confirmed active employees in the dataset drew particular concern, given that portions of the records appear to touch on undercover personnel.
A pattern of DHS breaches
This is not the first substantial data exposure tied to DHS. In 2014, a breach potentially affected as many as 390,000 current and former employees, applicants, and contractors. In 2018, the department notified nearly 250,000 people after another incident. Earlier this year, security firm GitGuardian found a publicly accessible GitHub repository containing credentials for privileged AWS GovCloud accounts and internal CISA systems, with the exposure dating back to at least November 2025.
Last month, the hacking group ShinyHunters published a separate spreadsheet containing records on roughly 5,000 alleged FBI employees, including home addresses and emergency contacts, framing that release as retaliation for an FBI advisory about the group.
DHS confirmed it is investigating the current incident. "DHS is aware of a potential breach and is actively working to address the situation swiftly and effectively," as mentioned by a spokesperson, adding that the department would release further details as they became available. DHS did not respond to additional requests for comment by publication time.
ENGIE, one of the world's largest energy companies, has notified customers in France that an unauthorized third party accessed their personal data through a marketing platform used by the company's business partners, the company confirmed this week.
The breach notification letters, dated October 23, went to affected customers after ENGIE said it detected "unusual data access activity" on the partner tool. The company has not stated exactly when the intrusion took place or how long the attacker had access before it was caught.
According to the notifications, the data the intruder obtained includes customers' first and last names, mailing addresses, email addresses, and phone numbers. It also includes two types of energy infrastructure identifiers specific to the French grid: the Delivery Point identifier (PDL) and the Metering and Estimation Point identifier (PCE). Both codes are tied to a customer's physical connection to the gas and electricity supply network. Customer IDs and contract numbers were also taken.
ENGIE said no banking data was involved, and that the breach was confined to the partner-facing marketing platform rather than any of its internal systems. The scope of the incident is currently limited to its French customer base, though the company has not said how many customers received notifications.
"We have cut off the attacker's access to the platform, notified the relevant authorities, and are directly informing each affected customer," the company said in a statement.
Customers were advised to stay alert to unsolicited contact and potential phishing attempts in the wake of the exposure.
No ransomware group or extortion actor had publicly claimed responsibility for the breach at the time of publication.
A Company With a Recurring Target on Its Back
ENGIE operates across 30 countries, employs more than 90,000 people, and posted €71.9 billion in revenue last year. Its scale across utilities, renewables, and energy infrastructure makes it a high-value target for threat actors looking for customer data at volume.
This latest breach is not the first time attackers have made it inside ENGIE's wider corporate ecosystem. Approximately a year ago, the Scattered LAPSUS$ Hunters group claimed it had breached a Salesforce instance belonging to Engie Records, the retail energy subsidiary of ENGIE North America, and leaked records from the intrusion. Engie Records appeared on the group's leak site as the 27th of 39 organizations allegedly hit through the same Salesforce-related campaign, with around 3GB of data listed.
Before that, in August 2023, a separate incident affected roughly 110,000 French ENGIE customers. In that case, a hacker known online as "HommedeLombre" reportedly got into ENGIE's systems through an external contractor's network, a technique also used in the Pôle Emploi breach around the same period. That attacker exposed names, email addresses, and phone numbers, and later said the intrusion was meant to demonstrate that "nothing is ever secure," citing rising gas prices as a grievance. ENGIE filed a complaint with authorities following that incident and said it had brought the affected system under control.
If we look closer to understand the link here, the three incidents point to a recurring problem: ENGIE's data, whether held by internal systems, subsidiaries, or third-party partners, keeps ending up in attackers' hands.
Why Energy Sector Customer Data Is Valuable
The combination of contact information and energy-specific identifiers like PDL and PCE codes makes the stolen data more useful to attackers than a standard contact list. Those codes link a name and address to a specific gas or electricity metering point in the French national grid, which means the data could be used to convincingly impersonate ENGIE in phishing campaigns or to target customers with fraudulent offers around energy billing or contracts.
France's energy market also went through a turbulent period of price volatility in recent years, which means many customers have been actively comparing suppliers and receiving legitimate outreach about tariff changes. That context makes it easier for fraudsters to craft believable messages that reference contract numbers, delivery point details, and billing information, exactly the kind of data now in circulation.
ENGIE said it has notified the relevant authorities, as required under GDPR. French data protection rules mandate that breaches of personal data be reported to the CNIL, the national data protection authority, within 72 hours of detection, and that affected individuals be notified without undue delay when the breach poses a risk to their rights and freedoms.
As of now, ENGIE has not attributed the breach to any specific threat actor, and it is unclear whether the platform through which the data was accessed belonged to an external vendor or an internal partner system. The investigation appears to be ongoing.
Data Magecart, a Brazilian group of hackers, compromised the analytics script used by e-commerce platform Convertr, potentially revealing payment information provided by customers to dozens of Brazilian fashion brands. During the attack, which was detected by cybersecurity firm Sansec on October 24, 2026, malicious code was injected into Convertr's Plausible analytics tracker.
By modifying a JavaScript file loaded into Convertr's merchant checkouts, the attackers allowed the card skimmer to collect sensitive information during online purchases by modifying the JavaScript file. The data obtained was comprised of card numbers, expiration dates, CVV security codes, cardholder names, and Brazilian CPF taxpayer identification numbers.
The information was transmitted to a server controlled by the attacker at 1x0.is. Online shopping and checkout services are provided by Convertr to dozens of Brazilian fashion retailers. According to the platform, its merchants have processed more than R$2 billion in sales. Due to the fact that the affected analytics tracker was distributed throughout its merchant network, compromising one file created a potential supply chain risk that extends beyond one individual online store.
The malicious script was detected by Sansec after a clean version was captured earlier on October 24th. In October, the attackers modified the skimmer in order to target Convertr's payment API field names, making it more effective in capturing payment information. Researchers also reported that the compromised tracker continued to serve on October 26, despite efforts to notify Convertr.
As Sansec has been tracking the Brazilian Magecart group since July 2024, the incident represents a significant development in its activities. The group has previously targeted individual online stores using Magento, OpenCart and WooCommerce, mainly in Brazil. With the Convertr compromise, Sansec has shifted from infecting individual stores to compromising a service shared by multiple businesses, resulting in the first supply chain attack attributed to the group.
An unpatched installation of Plausible Community Edition, an open-source web analytics platform, is believed to have been the source of the attack. Versions 3.0.0 through 3.2.0 were affected by CVE-2026-8467, a critical vulnerability that could allow unauthenticated command execution through an exposed component of the /storybook component.
Convertr reported installing version 3.0 in 2025 and not updating it prior to the incident. On May 15, 2026, Plausible released version 3.2.1 which fixed the vulnerability. Since researchers were not able to access the platform’s server logs, Sansec has not confirmed that the vulnerability was exploited to gain access. Therefore, it remains unclear what specific method was used to compromise the analytics server. Furthermore, the group has consistently targeted Brazilian payment systems as a focus for their methods.
According to Sansec, its skimmers exhibit recurring characteristics, including the use of short-lived domains as recipients of stolen information, and endpoints containing Portuguese names related to card payments. Other variants have also been developed to attack payment services, including e.Rede, PagSeguro, Pagar.me and Mercado Pago.
Another version is reported to replace genuine PIX payment QR codes with malicious codes. Convertr confirmed on October 27 that Plausible had been updated with a patched version following the discovery of the malicious script. In addition to notifying affected merchants, payment providers, and relevant authorities, the company also verified that the tracker hosted on Convertr's analytics server was free of infection.
While it is important to remove malicious code, it does not necessarily eliminate all immediate risks for all shoppers. Sansec stated that browsers may retain cached copies of infected scripts for up to 24 hours following the server-side cleanup, potentially allowing the malicious code to remain active during that period.
Payments made by Brazilian customers through checkout addresses containing checkout.convertr from October 24 onward should be blocked and replaced by their banks. It is also recommended to monitor transactions for suspicious activity involving CPF identification numbers in order to identify suspicious activity.
A Sansec recommendation for organizations using Plausible Community Edition is to update the version to 3.2.1 or later and to review server access logs for requests to the exposed path of /storybook. Upon detecting evidence of exploitation, the affected server should be rebuilt, secrets rotated, tracker files checked against the official release, and a more thorough investigation conducted. The incident emphasizes the wider risks associated with shared web infrastructure.
Multiple businesses can be affected by compromised analytics scripts without the attacker having to breach each merchant individually. To reduce the risk of similar attacks, it is vital that software be updated, scripts loaded on payment pages are monitored, and unauthorized outbound connections are restricted.
This incident illustrates the dangers posed by compromised third-party scripts used on checkout pages. Preventing digital skimming attacks requires timely software updates, continuous script monitoring, and stronger protection of payment infrastructure.
A 44-year-old Chinese national has been brought to the United States from the Netherlands to answer federal charges tied to a cryptocurrency investment scheme that drained nearly $37 million from 174 American victims.
Zhen Zhao was arraigned in California after his extradition, prosecutors said, following a federal indictment handed down in August 2025 charging him with conspiracy to commit money laundering. If convicted, he faces up to 20 years in federal prison.
Zhao is accused of running what investigators call a "pig butchering" operation, a type of confidence scam that has become one of the fastest-growing financial crimes in the world. The name reflects how the fraud works: operators spend weeks or months cultivating trust with their targets before stealing everything from them at once.
How the scheme worked
According to court documents, Zhao and his co-conspirators reached victims through unsolicited text messages, social media platforms, phone calls, and online dating services. The initial contact was typically low-stakes, a misdirected text, a friendly exchange that seemed accidental, or a casual introduction through a dating app. Over time, the operators steered conversations toward investment opportunities, eventually directing victims to what appeared to be functioning cryptocurrency trading platforms.
The platforms were fabricated. Built to resemble real exchanges, they showed account balances growing steadily over time, giving victims every reason to keep putting money in. When victims eventually tried to withdraw their funds, they were blocked, hit with invented fees, or simply cut off. Their money was already gone.
The ring funneled more than $36.9 million from U.S. bank accounts into an account at Deltec Bank in the Bahamas, registered under the name Axis Digital Limited. From there, the bank was directed to convert the deposited money into Tether, a dollar-pegged stablecoin widely used in fraud for its stability and ease of transfer. That Tether was then moved to a digital asset wallet controlled in Cambodia, where it was passed up to the leaders of scam centers operating in the region.
Cambodia has become a significant hub for this type of operation. Criminal syndicates there have turned large-scale cryptocurrency fraud into core business, often staffing compound facilities with trafficked workers from across Asia who are forced to run these schemes under threat of violence. The money chain in the Zhao case reflects that geography directly.
Eight accomplices, two already sentenced
Zhao was not running the operation alone. Eight co-conspirators have already pleaded guilty in connection with the same scheme. Two have been sentenced so far, one to 51 months and another to 46 months in federal prison. The remaining cases are moving through the courts.
The extradition itself was the result of months of legal coordination between U.S. prosecutors, the State Department, and Dutch authorities. The Netherlands, which maintains a functioning extradition treaty with the United States, processed Zhao's transfer back to face trial in California.
A problem that keeps growing
This case sits inside a much larger crisis. The FBI's 2025 Internet Crime Report recorded more than $8.6 billion in losses from investment scams over the course of a single year, up from $6.5 billion the year before. Those figures came from roughly 73,000 complaints, and investigators routinely note that reported numbers reflect only a portion of real losses, since many victims never file a report out of embarrassment or because they do not know where to turn.
Pig butchering has become the dominant form of cryptocurrency fraud in the United States. The FBI ran a proactive victim notification program that reached more than 4,300 pig butchering victims in a single year, warning people before they lost everything. Despite those efforts, the dollar figures keep climbing.
The Department of Justice has treated these cases as a priority. In December 2023, federal prosecutors in California charged four people with laundering more than $80 million connected to similar cryptocurrency investment scams, using shell companies and hundreds of individual banking transactions to move stolen money internationally. Prosecutors at the time described the mechanics as nearly identical to what Zhao and his network allegedly ran.
What victims should do
Anyone who believes they were targeted by a pig butchering scam can file a report with the FBI's Internet Crime Complaint Center at IC3.gov. Investigators ask that victims preserve all records of communications, platform names, cryptocurrency wallet addresses, transaction IDs, and any banking information they shared during the fraud.
For Zhao, the arraignment in California is the start of what will likely be a long legal process. With eight alleged co-conspirators already pleading guilty, prosecutors appear to have a functioning case built around his network. Whether he opts for trial or takes a similar path remains to be determined.
Due to a disruption of access to DreamHost's File Manager and webmail services as a result of an incident, certain email and FTP/SFTP accounts were forced to reset their passwords. Although the hosting provider described the action as a precautionary security measure, it has not yet revealed the cause of the incident or confirmed whether any accounts have been accessed without authorization.
When DreamHost first detected connectivity problems affecting its file manager on the web at files.dreamhost.com on October 23, 2026, the disruption was initially reported. As a consequence, some webmail users experienced login failures, while FTP/SFTP access was also affected by the issue. As a result, the company reset passwords for affected accounts and temporarily restricted access until new credentials could be established.
When a DreamHost account owner assigns a replacement password to the affected mailbox and file transfer users, the users cannot sign in. By the weekend, DreamHost mailed recovery instructions to all affected account holders in stages and confirmed to all affected account holders that all were notified by October 25.
In October, the company reported that engineers had deployed a fix and had restored File Manager functionality. Monitoring continued to ensure that the service continued to operate, however password changes for affected accounts continued to be required. Since limited information has been released by the company about the incident, customers have expressed concern.
Neither DreamHost nor the company has identified the root cause, disclosed the number of accounts affected, or confirmed whether any email messages, stored files, or login credentials have been compromised. Also, the provider advised users to review their mailbox forwarding settings and remove any unfamiliar destinations. This setting can be abused in order to redirect sensitive communications outside a company, thereby making it a crucial element of account security.
DreamHost has, however, not confirmed that unauthorized forwarding rules have been created in this incident. Additionally, customers have expressed concern about the lack of detailed explanations for the disruptions in service as well as mandatory password changes. Despite speculation about a possible compromise, no publicly available confirmation has been provided to indicate that an attack or data breach has occurred.
According to DreamHost, account owners should update stored credentials across connected applications and review account settings in order to complete the recovery process. Email clients, FTP/SFTP software, website backup tools, deployment systems and plugins relying on previously stored credentials may be affected by password changes.
In order to avoid the possibility of affected users losing access to their hosted mailboxes, the company recommends that replacement passwords be shared through private channels, such as telephone calls or secure text messages. The recovery guidance provided by DreamHost specifies that mailbox passwords can be changed under “Mail > Manage Email” in the control panel, and FTP/SFTP credentials can be updated under “Websites > SFTP Users & Files”.
If you changed your password before the reset process was completed, you should verify that your new password remains valid as well. Password changes may take up to 15 minutes to become effective. There is no indication that incoming email is reaching affected mailboxes, and that FTP/SFTP data is still stored on the provider's servers.
In addition to these assurances concerning service and data availability, it is also recommended that website owners conduct routine site checks to determine whether unauthorized access occurred prior to the password reset. Considering that FTP/SFTP credentials provide access to website files, it is important to identify suspicious changes by reviewing recently modified files, unfamiliar administrator accounts, and unforeseen scheduled tasks.
There has been no evidence published to indicate that DreamHost-hosted websites were altered as a result of the incident. This episode also underscores the importance of using third-party hosting providers for security reasons. When a hosting company encounters a disruption, several connected services may be affected at once, especially when email addresses and file transfer credentials are handled by the same provider.
In order to ensure that essential operations are resumed after the password change, DreamHost has repeatedly warned customers that it will never send customers passwords by email. Businesses using DreamHost may need to check integrations and automated processes reliant on these accounts. Rather than logging into the control panel through unsolicited messages, account owners should access the control panel directly.
No public explanation has yet been provided by the company as to what triggered the incident or the number of affected customers has been confirmed. In the interim, a central question remains as to whether the incident involved unauthorized access, how many accounts were affected, and if any customer information was revealed. Despite DreamHost's password reset process and restoration of File Manager access, the broader issues associated with the incident haven't been resolved.
DreamHost's restoration of File Manager access marks progress in the recovery process, but the absence of an identified root cause leaves the incident's broader security implications unresolved. While the company has yet to clarify the cause of the incident, and whether any customer accounts or data has been accessed, it remains unclear how the incident will impact the security of the company.