FBI links $6.3 billion Binance crypto heist to North Korean hackersThe FBI attributed the roughly $6.3 billion Binance theft of about 29 October 2026 to North Korea's TraderTraitor (Lazarus Group, Jade Sleet, APT38). Binance traced the breach to a compromised DevOps engineer's laptop that gave access to a service container used to submit unauthorized withdrawals across ten blockchains. The FBI published 628 laundering addresses and linked the group to earlier thefts at Bybit, DMM Bitcoin, Bitget and Drift.
bleepingcomputer.comarticlePublished and added 1 Nov 2026π‘οΈ Security
Binance Hack: Everything You Need to Know About the Biggest Crypto Heist in HistoryDecrypt's explainer on the roughly $6.4 billion theft from Binance hot wallets across about 10 blockchains. Binance traced it to a compromised DevOps engineer laptop plus further breach points, and on Ethereum the attacker used 50 pre-signed EIP-7702 authorizations to turn a hot wallet into a sweeper. Chainalysis and TRM Labs attribute it to TraderTraitor; Tether and Circle froze about $2.3 billion.
decrypt.coarticlePublished and added 31 Oct 2026π‘οΈ Security
Binanceβs $6.3 Billion Hack Puts Developer Machine Security in FocusStepSecurity's analysis of Binance's 29 October 2026 incident, which Binance puts at about $6.3 billion in affected assets. It covers Binance's disclosure of a possible DevOps laptop compromise, and TRM Labs and Elliptic findings on 50 EIP-7702 authorizations and a persistent delegation. It links this to the Nx, OVHcloud CLI and Claude Code extension compromises, gives an investigation checklist, then describes StepSecurity products.
stepsecurity.ioarticlePublished and added 30 Oct 2026π‘οΈ Security- President Trump says theyβre looking into Binance hack as calls grow for crypto rules
The Block reports that Binance lost about $6.3 billion in a hack on 29 October 2026. Co-CEO Richard Teng said a compromised DevOps engineer's laptop gave access to a service container used to submit unauthorized withdrawals, and TRM Labs attributed the theft to North Korea's TraderTraitor. The rest covers reactions: President Trump said on 30 October he was looking into it, CFTC Chair Michael Selig and The Digital Chamber urged federal exchange rules, and senators disputed whether the Clarity Act would have allowed freezes.
theblock.coarticlePublished and added 30 Oct 2026π‘οΈ Security
Weekly Research Brief: Binance Hacked; Hyperliquid on Wall Street; Prediction Marketsβ Brazil βMissβGalaxy Research's weekly brief of 30 October 2026 opens with the Binance hack: about $6.3b drained across 10 blockchains, attributed by TRM Labs and Chainalysis to TraderTraitor (Lazarus-linked). The attacker used EIP-7702 with 50 pre-signed authorizations on Ethereum, and Binance's preliminary finding is a compromised DevOps laptop reaching a service container. Tether and Circle froze about $2.6b. The other sections cover Hyperliquid and prediction markets.
galaxy.comarticleAdded 30 Oct 2026π‘οΈ Security
Here We Go Again: Binance Loses $6.3b in Largest Robbery in HistoryGalaxy Research newsletter on the roughly $6.3b drained from Binance across 10 blockchains, which TRM Labs and Chainalysis attribute to TraderTraitor. On Ethereum the attacker used EIP-7702 to turn a hot wallet into a sweeper contract backed by 50 pre-signed authorizations. Binance's preliminary finding is a compromised DevOps laptop, with no wallet key leak. Tether, Circle, Ripple and World Liberty froze about $2.7b; Galaxy also assesses Binance's ability to cover losses.
galaxy.comarticleAdded 30 Oct 2026π‘οΈ Security
Binance Just Suffered the Biggest Hack in Crypto History. What Now?Bankless report on the Binance hack of $6.3 billion, which Binance's preliminary investigation traced to a compromised DevOps engineer's laptop with access to withdrawal-authorizing systems. TRM Labs found valid EIP-7702 authorizations on Ethereum, and nine other chains were drained through normally signed transactions. TRM and Chainalysis link it to North Korea's TraderTraitor. Tether and Circle froze about $3 billion, and Binance says SAFU and corporate cash will cover the losses.
bankless.comarticlePublished and added 30 Oct 2026π‘οΈ Security
Secret Service, FBI Join Binance Hack Probe as Circle Freezes $823 MillionDecrypt reports that Binance is working with the FBI and U.S. Secret Service after a theft of about $6.4 billion, which TRM Labs and Chainalysis attribute to North Korea's TraderTraitor group, also linked to the February 2025 Bybit hack. Circle froze about $823 million in USDC and Tether froze USDT, though the page gives differing Tether totals. Binance first suspected a compromised DevOps engineer laptop, found more breach points, and saw no evidence of leaked wallet private keys.
decrypt.coarticlePublished and added 30 Oct 2026π‘οΈ Security
Binance hack: the largest robbery in financial historyBinance hack analysis from 21shares on the 29 October 2026 theft of about $6.3 billion from Binance. Binance's initial finding points to a compromised DevOps engineer's laptop with no sign of a leaked wallet key. Chainalysis attributes it to North Korea with high confidence, and about $3 billion was frozen by Tether, Circle and the Arbitrum Security Council. The attacker also borrowed about $44.6 million of WETH on Aave. Binance says SAFU and company funds will cover all losses.
21shares.comarticlePublished and added 30 Oct 2026π‘οΈ Security- Binance says it has $6.34 billion ready to cover hack losses
The Block reports that Binance says it has set aside $6.34 billion of its own funds to cover a hack it puts at about $6.3 billion. Co-CEO Richard Teng says the entry point was a compromised DevOps laptop and no private key leak was found. About $3 billion was frozen by Tether, Circle, Ripple and others, withdrawals are suspended, and TRM Labs sees parallels with North Korean attacks. Technical detail is thin.
theblock.coarticlePublished and added 30 Oct 2026π‘οΈ Security
Binance hack: how a compromised developer laptop can lead to a $6.3 billion breachAikido Security's analysis of the roughly $6.3 billion Binance incident, which Binance says may have started with a compromised DevOps engineer's laptop. It sets out what is known (no private key leak, TraderTraitor attribution by TRM Labs and Chainalysis, additional breach points) and a plausible chain from laptop credentials to a withdrawal service. It compares the 2025 Bybit theft and lists mitigations.
aikido.devarticlePublished and added 30 Oct 2026π‘οΈ Security
Binance Finds 'Additional Points of Breach' in $6.3B HackBinance estimated the October 2026 security incident at about $6.3 billion and said it found "additional points of breach" beyond the compromised DevOps engineer laptop it first named. The attacker reached a service container and submitted unauthorized withdrawals, with no wallet private key leak found. Arkham counted $6.01 billion taken from hot wallets on nine chains; Tether and Circle froze about $1.8 billion in stablecoins. About $3 billion is frozen onchain; withdrawals stay suspended.
decrypt.coarticlePublished and added 30 Oct 2026π‘οΈ Security
Binance links $6.3 billion crypto theft to compromised DevOps laptopBinance linked the theft of about $6.3 billion in crypto to a compromised DevOps engineer's laptop, which let attackers reach a service container and submit unauthorized withdrawals. TRM Labs and Chainalysis attribute the 29 October 2026 attack to North Korea's TraderTraitor. About $2.7 billion was frozen, and the attackers hold about $2.4 billion. Binance has found no evidence of a leaked wallet private key.
bleepingcomputer.comarticlePublished and added 30 Oct 2026π‘οΈ Security
$6 Billion Binance Hack Bears Hallmarks of North Koreaβs TraderTraitorThe Binance hack of 29 October 2026 drained about $6.36 billion across ten blockchains in roughly 20 minutes, according to TRM Labs. TRM attributes it with high confidence to North Korea's TraderTraitor, citing a mixer-funded operator wallet, pre-signed transactions and overlap with the Bybit and KelpDAO hacks. Binance's early findings point to a compromised DevOps engineer laptop. Stablecoin issuers froze about $2.7 billion.
securityweek.comarticlePublished and added 30 Oct 2026π‘οΈ Security
Binance probes a suspected cryptocurrency breach: $6.3B affected, about $3B frozenBinance disclosed a suspected security incident on 29 October 2026, estimating $6.3 billion affected and about $3 billion frozen. Binance's early finding is that a compromised DevOps engineer's laptop let an attacker reach a service container and submit unauthorized withdrawals, with no evidence of wallet private-key leakage. TRM Labs suspects TraderTraitor, the group tied to the February 2025 Bybit theft. Tether, Circle and Ripple froze funds.
en.cryptonomist.charticlePublished and added 30 Oct 2026π‘οΈ Security
GitHub Universe 2026: Evolving every layer of the stackGitHub Universe 2026 recap in which GitHub presents its agentic software delivery vision and new Copilot products: the Copilot app, Copilot Fusion multi-model routing, Copilot projects, session continuity, automations that learn from outcomes, and code review Max. GitHub Enterprise customers can use all Copilot features without a separate subscription. GitHub also reports added capacity, a multi-region Azure migration and a redesigned Git architecture.
github.blogarticleAdded 29 Oct 2026, published 28 Oct 2026π§ AI
TLS Flaws Found in GoAhead Web Server Used in Hundreds of Millions of DevicesFoxIO disclosed three TLS flaws in the GoAhead embedded web server from EmbedThis, used on hundreds of millions of IoT, OT and network devices. CVE-2026-115881 (CVSS 9.1) leaves revoked client certificates accepted under mTLS with OpenSSL; CVE-2026-115884 (7.4) bypasses chain-length limits with LibreSSL; a third Mbed TLS bug (5.9, no CVE) weakens TLS 1.2 DHE. GoAhead 6.1.1 fixes the OpenSSL and Mbed TLS issues, and FoxIO released PoC code and fingerprints.
securityweek.comarticlePublished and added 28 Oct 2026π‘οΈ Security
Vendor Key Leak Puts Data of 238,000 Denver Health Plan Members at RiskDenver Health Medical Plan is notifying 238,083 members that vendor SquareML leaked an access key on a public website. The key was online from 27 June 2025 until it was revoked on 18 August 2026 and gave read-only access to a database of names, dates of birth, health metrics, eligibility and admission data. DHMP found no evidence of misuse and reset passwords for all accounts with access.
securityweek.comarticlePublished and added 27 Oct 2026π‘οΈ Security- Unboxing Phishing Kits: Huntress Examines 3 Real Kits
Recap of a Huntress Tradecraft Tuesday session (October 2026) on phishing kits that target Microsoft 365 tokens, including EvilTokens (a device-code phishing campaign abusing Railway) and the Kali365 control panel. It explains device-code phishing, adversary-in-the-middle and token replay. It lists detections (unfamiliar cloud sign-ins, device-code auth, new devices) and response steps (revoke refresh tokens, remove rogue devices, block device-code flow).
huntress.comarticlePublished and added 22 Oct 2026π‘οΈ Security
eMudhra CA compromise: eight private keys, and one of them is 4eMudhra's eight intermediate CA certificates, chaining to emSign ECC Root CA - G3, had private keys below 256 (one is 4), disclosed on 17 October 2026 by a researcher known as Wayne. Browsers and Microsoft blocked them via revocation pushes, but curl, git, containers, language runtimes and IoT may still trust them. The post gives patched ca-certificates versions, test commands and the timeline.
aikido.devarticlePublished and added 22 Oct 2026π‘οΈ Security
eMudhra CA Compromise: The Trust Stores You Didn't Patch | Endor LabsThe eMudhra CA compromise (disclosed 20 October 2026) involves eight intermediate CA certificates whose private keys can be derived from the certificates themselves. They chain to AAA Certificate Services and three other roots. Browsers block them, but non-browser clients skip revocation and CT checks. Endor Labs finds 25 popular packages with frozen bundled root stores, 11 already patched, and gives a fingerprint-scanning script, test hosts and patch steps.
endorlabs.comarticlePublished and added 21 Oct 2026π‘οΈ Security
A company that vouches for websites had secret keys so weak that 8 of them were crackedeMudhra, an Indian certificate authority with over 60 million issued certificates, had eight CA private keys that were tiny integers such as 4, 56 and 237. Researcher Scott Helme recovered all eight from public certificates in under a second, and the keys were exposed from April 2025. Mozilla, Chrome, Apple and Microsoft blocked them between 17 and 20 October 2026, but curl, Python, Node.js, Go and Java accepted a forged Stripe API certificate because they skip revocation checks.
coindesk.comarticlePublished and added 21 Oct 2026π‘οΈ Security
Hackers Steal 1.8 Million Records From NikkeiNikkei disclosed a breach of 1.83 million records from a cloud service it uses for system development, accessed on 7 October 2026 with previously compromised credentials. About 150,000 records held names, addresses, emails, phone numbers and birth dates, and 120,000 held email addresses only. Nikkei revoked the credentials and notified regulators. It found no misuse as of 16 October, and it had disclosed an earlier Slack account breach less than a year before.
securityweek.comarticlePublished and added 20 Oct 2026π‘οΈ Security
TokenMaxxing: How to Get the Most Out of Your AI ModelsDecrypt guide to "tokenmaxxing" reframed as maximizing value per token rather than burning tokens. It gives tiered tips: pick smaller models for simple jobs, write one clear prompt, start new chats, cap output length, and use free models (beginner); Claude Code commands like /model, /clear, /compact, /context, /mcp, /effort and plan mode (intermediate); and prompt caching via cache_control, 50% batch discounts, and agent budget limits like --max-budget-usd (advanced). Includes context on Meta, Amazon and Uber token leaderboards and spend, a worked invoice-processing example where routing cut cost from $30 to $3.90, and the Jevons paradox in falling token prices.
decrypt.coarticlePublished and added 17 Oct 2026π§ AI
AI generated viral genomes yield 16 viable phages, prompting safety concernsReports a Science study from Stanford University and the Arc Institute in which Evo, a genome language model trained on sequences from across the domains of life, generated thousands of bacteriophage genome designs targeting E. coli. About 300 were built and tested, and 16 produced viable viruses. A mixture of the AI-designed phages overcame resistance in some E. coli strains where a comparable mixture of natural phages did not. The article also covers a Johns Hopkins Center for Health Security commentary saying governance lags behind generative genome design, and a more cautious biosafety assessment from an outside expert.
en.cryptonomist.charticlePublished and added 16 Oct 2026π§ AI
F5, Juniper Networks Patch Critical VulnerabilitiesSecurityWeek reports F5 fixed 11 NGINX vulnerabilities. Three are critical: CVE-2026-15176 and CVE-2026-93479 are unauthenticated buffer overflows via crafted HTTP requests, and CVE-2026-97205 is memory corruption. All three can lead to RCE if ASLR is disabled or bypassed. Juniper Networks published 17 advisories covering over 150 flaws in Junos OS and Junos OS Evolved, plus four in Cloud-Native Router. About two dozen are critical, with root code execution, device takeover, kernel panic and an off-by-one buffer overflow. Neither vendor reports exploitation in the wild.
securityweek.comarticlePublished and added 16 Oct 2026π‘οΈ Security
Staying Evergreen: How we automated secure access and repo hygiene in a shared orgGitHub engineers describe Evergreen, a Go-based GitHub App that runs quarterly outside-collaborator access reviews and archives stale repositories in a shared org. It uses scheduled Actions with repository_dispatch, JSON state files in git as the audit trail, checklist issues (IssueOps) closed to trigger revocation, and custom properties for ownership and exemptions. Design principles include fail-secure/fail-closed revocation, never deleting data, dry-run rollout, Splunk logging, and proactive pacing against GitHub's secondary rate limits.
github.blogarticlePublished and added 15 Oct 2026π‘οΈ Security
VulnBump: Can AI Agents Fix Vulnerable Dependencies Without Breaking the Build?Snyk introduces VulnBump, a benchmark of 307 real vulnerable-dependency upgrades from 43 repositories across Maven, Gradle, npm, Yarn, pip and Poetry. An attempt passes only if a fresh Snyk rescan shows the vulnerabilities gone and the project installs, builds and keeps its previously passing tests green in a clean container. On Claude Sonnet 5.5, Snyk's Evo Remediation Agent passed 90.2%, Claude Code with Snyk scan and target version 77.5%, unaided Claude Code 59.6%, and a non-AI package-manager bump baseline 46.9%. Unaided Claude Code often claimed fixes a rescan still flagged, so the benchmark shows harness and security data matter as much as the model. The harness and 43 cases are open-sourced.
snyk.ioarticlePublished and added 15 Oct 2026π§ AI
VulnBump: Can AI Agents Fix Vulnerable Dependencies Without Breaking the Build?Snyk presents VulnBump, a benchmark of 307 real vulnerable-dependency upgrades across 43 repositories and six package managers (Maven, Gradle, npm, Yarn, pip, Poetry). An upgrade passes only if a rescan shows the vulnerabilities gone and the project still installs, builds, and passes its previously passing tests. On Claude Sonnet 5.5, Snyk's Evo Remediation Agent passed 90.2%, Claude Code with Snyk scan 77.5%, Claude Code unaided 59.6%, and a plain package-manager bump 46.9%. Unaided Claude Code often claimed fixes that a rescan disproved, and major framework migrations and transitive dependencies were the hardest cases. The harness and the 43 cases are open-sourced.
snyk.ioarticlePublished and added 15 Oct 2026π‘οΈ Security- Passkeys Raise the Bar. Hereβs Where Attackers Can Still Get In.
Huntress post on where accounts remain exposed after a passkey rollout. It covers passkey-themed social engineering, the EvilTokens device-code phishing campaign (344 organizations in about 16 days), weak enrollment and recovery, SpecterOps research on Windows WebAuthn hooking on compromised endpoints, and the trade-offs between synced and device-bound passkeys. It closes with ITDR-style post-login monitoring, containment steps (revoke sessions, remove rogue authenticators, hunt inbox rules, OAuth grants, forwarding), and a five-question deployment checklist.
huntress.comarticlePublished and added 14 Oct 2026π‘οΈ Security
Showing 30 of 77
Show more