Binance loses US$ 6.3 billion; GitLab CVSS 10 flaw exploited
Record theft of US$ 6.3 billion at Binance and five critical flaws confirmed in active exploitation.

The 30-second summary
- Binance suffers the largest cryptocurrency theft in history: US$ 6.36 billion stolen; US$ 3 billion frozen, US$ 3.3 billion unaccounted for.
- Claude Code extension was tampered with on the Cursor marketplace and installed hidden remote access; up to 5 thousand affected, update released.
- PHP2Shell evolves into real intrusions: researcher sees live attacks with signs of ransomware; PHP 8.1 and earlier remain without a fix.
- CISA (US cybersecurity agency) confirms GitLab CVSS 10 exploited: remote code without login, federal deadline on November 1.
- Flaw 9.8 gives total control of Linux servers: AI-created exploit works; Ubuntu and Red Hat remain without a fix.
Binance loses US$ 6.36 billion in the largest cryptocurrency theft in history
Hackers stole US$ 6.36 billion from Binance on October 29, in the largest cryptocurrency theft ever recorded. According to TRM Labs, the North Korean group TraderTraitor is the author; about US$ 3 billion has already been frozen.
US$ 3.3 billion remains without a trace. Binance says user funds are safe, that the loss belongs to the exchange and that it will cover the losses. Bitcoin fell about 2%, with more than US$ 1.5 billion in forced liquidations.
For the technical team
Theft of about US$ 6.36 billion from Binance starting on October 29, with movement across 10 blockchains, attributed by TRM Labs to TraderTraitor. Issuers such as Tether and Circle froze part of the assets. Initial vector not reported in the sources.
- Affected
- Binance; the exchange's own funds, not customers'
- Exploitation
- confirmed active
- Fix
- Withdrawals suspended on several networks; asset freezing with issuers; losses covered by the SAFU fund, according to Binance
Takeaway: For high-value assets, the final loss depends on the speed of detection and freezing.
Sources: @vxunderground, @WatcherGuru, @mert, @pashov
On the radarFollow this incident live →Claude Code extension with backdoor reaches up to 5 thousand Cursor users
A tampered version of the Claude Code extension was distributed through the Cursor IDE marketplace and installed hidden remote access on machines. Cursor says at most 5 thousand users downloaded version 2.1.313, not developed by Anthropic.
Whoever installed it may have active remote access on the development workstation, exposing code, credentials and repositories. Cursor took down the marketplace, neutralized the malware with the providers and asks for an update to version 2.1.314.
For the technical team
Version 2.1.313 of the Claude Code extension for VS Code, distributed on the Cursor marketplace, contained a malicious loader that installed a persistent SSH backdoor, added the attacker's SSH key and sent host data, according to The Hacker News. Cursor removed the package and reactivated the marketplace.
- Affected
- Claude Code extension for VS Code version 2.1.313, via the Cursor marketplace; up to 5,000 users
- Exploitation
- confirmed active
- Fix
- Update to Claude Code for VS Code 2.1.314; locate the malicious package using the Cursor guide and review SSH keys
Takeaway: A package installed by a developer is an intrusion vector; an extension inventory must exist before the incident.
Sources: @cursor_ai, @mattjay, @TheHackersNews
On the radarFollow this incident live →PHP2Shell: live intrusions point to ransomware, says researcher
A researcher observes intrusions in real time against real organizations using the PHP PHP2Shell flaws, with assessment of intent to deploy ransomware. CISA (the US government's cybersecurity agency) and Palo Alto Networks had already confirmed active exploitation.
The risk already reaches the entire operation: companies report about six exploitations, with 25 servers under total control in four countries and movement into the Active Directory, the central login of corporate networks.
For the technical team
CVE-2026-109618 and CVE-2026-109619 are use-after-free flaws in PHP that allow unauthenticated RCE in configurations that serve web requests: PHP-FPM, mod_php, php-cgi, FrankenPHP and LiteSpeed. Researcher reports live intrusions with ransomware assessment; three servers in an environment linked to the US government and lateral movement into the Active Directory. The chain also uses CVE-2026-46300 of the Linux kernel, already in the KEV.
- CVE
- CVE-2026-109618, CVE-2026-109619, CVE-2026-46300
- Affected
- PHP 5.4 to 8.5.11 in all branches that serve web; 8.1 and earlier without a fix from the project
- Exploitation
- confirmed active
- Fix
- PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, with service restart; also apply the kernel fix (CVE-2026-46300) and check for compromise
Takeaway: An applied patch only counts after restarting the service and confirming the running version.
On the radarFollow this incident live →Brotli gains a WordPress vector with public exploit in xmlrpc.php
The Brotli flaw gained a new vector in WordPress: a researcher published an exploit that attacks sites via /xmlrpc.php. CISA had already confirmed active exploitation of the flaw, with a federal fix deadline on November 10.
The flaw is embedded in products used everywhere: Node.js, Bun, Python.NET packages, Visual Studio, PowerShell and Palo Alto firewalls. Whoever processes compressed data from external sources is at risk of code execution. Running processes keep the vulnerable code until restart.
For the technical team
CVE-2026-111497 is an out-of-bounds write in Google's Brotli decoder (CVSS 9.2), exploitable without authentication with malicious compressed data. New vector via WordPress /xmlrpc.php with a public exploit. Also affects Envoy and Istio configured to decompress Brotli.
- CVE
- CVE-2026-111497
- Affected
- Brotli 1.0.3 to 1.2.0; Node.js 22.x/24.x/26.x before the fixes; EOL lines 20.x, 23.x and 25.x without a fix; Bun before 1.4.4; .NET, Visual Studio and PowerShell before the October 25 updates
- Exploitation
- confirmed active
- Fix
- Node.js 22.23.4, 24.22.1 or 26.12.1; Bun 1.4.4; Brotli/brotlicffi 1.2.1; Microsoft updates from October 25; restart services, rebuild containers and, until the Palo Alto fix expected for October 30, disable Brotli inspection
Sources: Microsoft, The Hacker News, @BleepinComputer
On the radarFollow this incident live →CISA confirms active exploitation of CVSS 10 flaw in GitLab
CISA confirmed active exploitation of CVE-2026-97229 in GitLab and requires federal agencies to fix it by November 1. The flaw, of maximum severity (CVSS 10.0), allows executing code on the GitLab server without any login, via a malicious expression in CI/CD configuration.
An attack was attempted against the GitLab of the Alpine Linux project, with no proof of success. The case exposes a blind spot: Alpine had already updated GitLab, but Ruby remained without a fix and the flaw was still exploitable; the server was rebuilt.
For the technical team
CVE-2026-97229 is an integer overflow in GitLab's CI/CD regex compiler, in Ruby's Onigmo engine, allowing unauthenticated RCE via regex in CI/CD configuration. Added to the KEV on October 29, 2026, with a federal deadline on November 1. According to CISA, other Ruby applications with the same engine may be affected.
- CVE
- CVE-2026-97229
- Affected
- Unpatched self-hosted GitLab CE/EE; fix released on October 12 in versions 19.4.2, 19.3.5 and 19.2.8
- Exploitation
- confirmed active
- Fix
- Update GitLab to 19.4.2, 19.3.5 or 19.2.8 and also Ruby; review logs and CI/CD configurations
Takeaway: Updating the application without updating the dependency underneath leaves the flaw exploitable.
Sources: CISA KEV, The Hacker News, @TheHackersNews, @DailyDarkWeb
On the radarFollow this incident live →XBOW reports critical flaw in web application of the US election commission
Security company XBOW claims to have found a critical remote code execution flaw in a public web application of the U.S. Election Assistance Commission, the American federal commission for election administration. According to XBOW, it was a resource and logistics calculator.
The flaw does not require login, according to XBOW, but the commission did not confirm the case. There is no CVE, fix or signs of exploitation in the sources. The application has no relation to electronic voting machines or voter registration.
For the technical team
XBOW reports an unauthenticated RCE of critical severity in a public EAC web application, described as a resource and logistics calculator. No CVE, patch or IoCs disclosed. The EAC did not confirm the case in the sources.
- Affected
- EAC resource and logistics application; technical details not disclosed
- Exploitation
- not reported in the sources
- Fix
- not reported in the sources
Linux kernel: AI-created remote root exploit; Ubuntu and Red Hat without patch
A 9.8 flaw in the Linux kernel allows executing commands with full power on servers, without a password and without user action. Anthropic demonstrated a working exploit created by an unreleased Claude model, not published and with no known attacks.
Ubuntu and Red Hat remained without a fix on October 29; Debian, Oracle, Amazon Linux and SUSE have already fixed part of the versions. The attack requires Multipath TCP active, a feature that combines several network connections; Go programs 1.24 or newer use it by default.
For the technical team
CVE-2026-98432 is a use-after-free due to a race condition in the kernel's IPv4 TCP stack, exploitable before application authentication, allowing execution as root on hosts with an MPTCP listener. The Anthropic model's exploit executed commands as root in about 53 minutes of testing and was not published. Red Hat rates it 5.9 because it considers the race hard to win.
- CVE
- CVE-2026-98432
- Affected
- Linux kernels from version 4.4 with a Multipath TCP listener; Ubuntu and RHEL without a patched package on October 29
- Exploitation
- not observed
- Fix
- Kernels 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3; workaround in Go: GODEBUG=multipathtcp=0
Sources: The Hacker News, @DarkWebInformer, @IntCyberDigest
On the radarFollow this incident live →Drupal confirms active exploitation of critical flaw in Commerce Core
Drupal confirmed that intruders are actively exploiting a flaw considered highly critical in the Commerce Core module, used by stores with shopping carts. The flaw allows bypassing access controls and can cause financial losses for merchants.
The real scale is still uncertain: Drupal did not disclose details or the scale of the attacks. Stores that use Commerce Core in versions 0.0.0 to 2.41 or 3.0.0 to 3.3.13 should follow the official advisories and fix as soon as possible.
For the technical team
CVE-2026-118539 is a missing authorization case in Drupal Commerce Core, with access control bypass confirmed in active exploitation by Drupal itself. CVSS not assigned; technical details and attack scale not disclosed.
- CVE
- CVE-2026-118539
- Affected
- Drupal Commerce Core 0.0.0 to 2.41 and 3.0.0 to 3.3.13
- Exploitation
- confirmed active
- Fix
- not reported in the sources
Sources: @TheHackersNews, The Hacker News
On the radarFollow this incident live →Built-in browsers of AI assistants have flaws; Codex and VS Code without a fix
Researcher Gal Weizman found flaws in the built-in browsers of Cursor, GitHub Copilot, Codex, VS Code and Claude Desktop, disclosed under the name EMBRACE. A hostile page opened in these browsers can execute code on the computer, read local files or spoof the displayed address.
Codex and VS Code were without a fix at publication, with users exposed, according to the blog. Source code, credentials and local documents, inside and outside the project folder, are within reach of a malicious page, with the user's privileges.
For the technical team
EMBRACE groups flaws in the built-in browsers of five desktop assistants: prompt injection leading to host RCE (Cursor), address bar spoofing (GitHub Copilot) and arbitrary reading of local files (Codex, Claude Desktop, VS Code). Codex and VS Code without a patch on the publication date.
- Affected
- Built-in browsers of Cursor, GitHub Copilot, Codex, VS Code and Claude Desktop; versions not reported in the sources
- Exploitation
- not reported in the sources
- Fix
- Update the assistants as the vendors release fixes; do not open untrusted pages or files in the built-in browser and review command approvals
Takeaway: A new tool on the developer's desktop is an attack surface that almost no one tests.
Sources: @WeizmanGal, r/netsec
On the radarFollow this incident live →VMware ESX: exploited logging flaw has a fix and deadline on November 11
The fix for the logging flaw in VMware ESX is in VMSA-2026-0006, with a federal deadline on November 11. CISA added CVE-2026-41709 to the KEV (CISA's list of flaws already used in attacks).
The flaw acts after the intrusion: according to CrowdStrike, the China-linked group Warp Panda used it as a zero-day. Whoever already has an administrator account executes operations without logging, removing the audit trail and delaying detection.
For the technical team
CVE-2026-41709 is insufficient logging in VMware ESX: an actor with admin privilege executes operations without logs. CrowdStrike attributes the zero-day use to the China-nexus actor Warp Panda, against the US legal sector. KEV on October 28, federal deadline November 11, use in ransomware listed as unknown.
- CVE
- CVE-2026-41709
- Affected
- VMware ESX; affected versions not reported in the sources
- Exploitation
- confirmed active
- Fix
- VMSA-2026-0006: builds ESXi-9.1.0.0-25370933, ESXi-9.0.2.0100-25595025 or ESXi80U3j-25429389 or newer; review admin holders and compare host activity with vCenter and network logs
Sources: CISA KEV, The Hacker News, SecurityWeek, @DailyDarkWeb
On the radarFollow this incident live →Wrapping up
The day repeated a clear pattern: critical flaws with fixes available being exploited now in GitLab, Drupal and Brotli, and ransomware assessment in PHP. In the Alpine case, the GitLab patch was not enough because Ruby remained without a fix. Finding early, fixing everything and checking afterwards is what prevents the incident.
If the patch was applied, how do we know the flaw is really gone?
Most of today's flaws already have a fix; the risk lies in what no one verified afterwards.
Talk to us