Opens in a new tab

Daily Security Briefing: Sunday, November 1, 2026

  • Home
  • Blog
  • Daily Security Briefing: Sunday, November 1, 2026
Daily security briefing featuring a breached vault and stolen Bitcoin coins

Today’s briefing covers 4 security issues reported in the last 24 hours, grouped by type: 1 breaches and data exposure, 2 ransomware and attacks, 1 patches and advisories. Each entry says who is affected and what to do, with links to the original reports.

Breaches and data exposure

TraderTraitor Linked to More Than $6 Billion Binance Theft

Who is affected: Binance, cryptocurrency users, and virtual asset service providers handling transactions linked to the stolen assets are affected; the FBI listed hundreds of Ethereum addresses, 19 Bitcoin addresses, and one Solana address.

The FBI attributed the theft of more than $6 billion in virtual assets from Binance on or about October 29, 2026, to North Korea-linked TraderTraitor actors. The stolen assets were converted primarily into ether and were expected to be laundered through DeFi and instant swap services. The FBI is working with the US Secret Service and IRS Criminal Investigations.

What to do: Crypto firms and virtual asset service providers should review the FBI’s listed addresses and block transactions with or derived from addresses used by TraderTraitor actors.

Sources: thehackernews.com, thenextweb.com

Ransomware and attacks

NetamLoader Targets Government Windows 10 Systems in Asia

Who is affected: Government organizations in Asia using a custom Windows 10 build exclusively used by government entities are affected.

A previously undocumented .NET assembly-loading framework called NetamLoader was deployed in a Windows cabinet archive placed in the Windows update download directory. The infection chain uses AppDomainManager injection to execute malicious code inside a legitimate application’s process, and the delivery vehicle and any broader compromise or data theft remain unknown.

What to do: Inspect government Windows 10 systems for the NetamLoader files and indicators, verify the integrity of update-package directories and trusted software supply chains, and investigate any unauthorized .NET assembly loading.

Sources: thehackernews.com

Hijacked DebugBear Script Took About $2.7 Million From Polymarket

Who is affected: Polymarket traders with 726 affected wallets are affected, with about $2.7 million being refunded.

A malicious script replaced the DebugBear page-speed script loaded by Polymarket on October 29. The code used signed-in traders’ browser access to sell positions, move funds to the hackers’ wallet, and obtain transaction approvals through the account’s signer. DebugBear said its domain registrar was compromised, with the malicious script targeting one customer’s website and no sign of a break-in to its own systems so far.

What to do: Polymarket users should review wallet transactions and account activity, revoke exposed trading credentials, and use any available refund or account-recovery process.

Sources: thehackernews.com

Patches and advisories

LXD and MicroCloud Flaw Allows Trusted Client Impersonation

Who is affected: LXD and MicroCloud deployments with network access to the HTTPS API and a trusted client’s public certificate are affected; LXD versions 4.0.14, 5.0.10, 5.21.8, and 6.9 are listed as affected before their fixed releases.

CVE-2026-112816 caused LXD and MicroCloud to accept a trusted client’s public certificate when it was attached behind another certificate in the chain, allowing impersonation without the private key. An attacker with network access to the HTTPS API could act as the trusted client, access the cluster and virtual machines, and potentially obtain root access to the host if the account was privileged.

What to do: Administrators should upgrade LXD and MicroCloud to the fixed versions listed by Canonical, and ensure the network API is enabled only where required and trusted client certificates are protected and monitored.

Sources: thehackernews.com

This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.

Sources

← All Articles