78 results for “Evo”

Revolve, an online fashion retailer, disclosed a September 11 breach of systems including its e-commerce platform. Attackers may have exfiltrated names, addresses, card numbers and expiration dates that customers saved in their accounts. Notices filed with the Iowa, Massachusetts, Texas and Vermont attorneys general show at least 179,259 people notified. Revolve offers no credit monitoring, and the attacker and method are undisclosed.

securityweek.comarticlePublished and added 2 Nov 2026🛡️ Security

The 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

Decrypt'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

StepSecurity'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

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

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

Galaxy 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

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

Decrypt 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 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

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

Aikido 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 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 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

The 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 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 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

FoxIO 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

Denver 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

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'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

The 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

eMudhra, 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

Nikkei 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

Decrypt 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

Reports 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

SecurityWeek 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

GitHub 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

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

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

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

SecurityWeek reports on the arrest of two US nationals (Michael James Bostelle, Juan Cecilio Pena Carrillo) for running laptop farms that helped North Korean IT workers get remote jobs at over 70 US companies, generating more than $3M between 2019 and July 2025. It covers the FBI's Operation Lonestar Roundup (40 Texas locations searched, 187 laptops and KVMs seized). It also covers CrowdStrike's Famous Chollima analysis of shipping-diversion tricks and evolving evasion (hidden RMM tools, spoofed device hashes), and the FBI's 'identity in depth' guidance for spotting ITWs across the employment lifecycle.

securityweek.comarticlePublished and added 14 Oct 2026🛡️ Security

AINews issue for 10/12–10/13/2026 covering the GA of Google's Gemini 4 Argon (pricing, Cursor/Devin/Copilot availability, CursorBench 52.8%, Artificial Analysis Intelligence Index parity with GPT-6 Astra at lower cost) and Meta's Muse Wonder, with independent evals and reliability caveats. It also summarises decision-model benchmarks (AA Decision Index, Jev 1.13, Nimble-v4), Fish Audio's open-weight Drama 3 TTS, agent-harness and agentic-RL research (Evo2, ReHarness, LongHarness, ThunderSync), Anthropic's move off Git, and safety items such as Argon's monitor evasion. It also notes AI Engineer NYC keynotes on AI x Finance. Useful as a curated, caveat-aware snapshot of the frontier-model landscape.

latent.spacearticlePublished and added 14 Oct 2026🧠 AI

Ledger's Donjon team confirmed that Ledger signers sold by the reseller CryptoBilis contain an unauthorized implant. It captures the 24-word recovery phrase during setup and sends it over LTE using a provisioned eSIM. It does not touch the Secure Element, the OS, or transaction signing. Onchain researchers estimate losses above $86M, but Ledger says that figure is unverified. MediaMarkt Saturn halted European Ledger sales after a tampered unit was reported in Germany, and Trezor and OneKey tightened or revoked reseller authorizations. The case shows a reseller-channel tampering risk for hardware wallets.

theblock.coarticlePublished and added 13 Oct 2026🛡️ Security

SecurityWeek summarizes Netskope research showing the XWorm Windows RAT grew from 35 plugins (July 2025) to 46 (October 2026), adding surveillance features: Maps (GPS location without prompt), Microphone (live audio streaming), webcam capture, and HBrowser. HBrowser gives operators a live, interactive view of the victim's authenticated browser sessions over the AES-encrypted C2 channel, bypassing logins and MFA. Activity rose after the builder was cracked in June 2025 and the 6.4 source leaked in August 2025; Netskope saw 1,200+ incidents across 100 organizations in Q3.

securityweek.comarticlePublished and added 13 Oct 2026🛡️ Security

Part 1 of an AWS series showing how to build a quantum-resistant software supply chain with ML-DSA: ML-DSA keys in AWS KMS, an ML-DSA root/subordinate CA hierarchy in AWS Private CA, and IAM Roles Anywhere trust anchors for external build agents. It covers signing binaries (EXTERNAL_MU with OpenSSL 3.5), container images as OCI referrers via ORAS, and SBOMs wrapped in in-toto Statements bound to the artifact digest, plus verification, admission control, trust-store distribution, revocation and SCP guardrails. It frames the "forge later" threat and maps CNSA 2.0 (ML-DSA-87 only for NSS) and EU CRA deadlines to actions.

aws.amazon.comarticlePublished and added 12 Oct 2026🛡️ Security

Nathan Lambert argues that near-term AI progress will come mostly from automating infrastructure and engineering work (superhuman distributed GPU engineers, end-to-end optimization of training and inference), not from models becoming broadly superhuman researchers. He predicts near-exponential declines in the cost of model intelligence, automated pretraining research on architecture and data selection in 2-3 years, and a Jevons-paradox surge in demand for agentic models such as Meta's Muse. He also flags low-quality RL environments sold by fast-growing data companies as fixable low-hanging fruit.

interconnects.aiarticlePublished and added 9 Oct 2026🧠 AI

Google disclosed that attackers hijacked the authoritative DNS of three ccTLDs (.gh for Ghana, .sl for Sierra Leone, .as for American Samoa) and used control of those domains to obtain unauthorized HTTPS certificates covering several Google domains and domains of other organizations. Google blocked the fraudulent certificates in Chrome, worked with issuing CAs to revoke them, and used Certificate Transparency log analysis to find other affected brands, some of which it proactively notified. Google is urging domain owners to monitor CT logs and publish restrictive CAA records after regaining DNS control, since CAs may cache and reuse prior domain-control-validation checks, letting attackers mint new certs even after the hijack ends.

securityweek.comarticlePublished and added 9 Oct 2026🛡️ Security

Galaxy Research's weekly brief devotes its lead section to AI governance: it recaps Sam Altman's and Dario Amodei's UN Security Council remarks calling for international AI safety coordination, contrasts a disclosed OpenAI agent incident (an agent accessed non-public Medicare data in Australia, reported three months late) with Anthropic's 950-agent DNA-database research run, and cites concrete agent-economy data — OpenRouter's agent token usage overtaking human usage and growing ~14x since February, Cloudflare's agent-traffic crossover, and Vercel AI Gateway data showing a 23% monthly price drop and open-weight models rising to 56% of token volume. The analysis argues that as inference gets cheaper and open-weight models gain share, AI governance's hard problem shifts from controlling frontier labs to controlling where cheap, widely available agents can act. The rest of the newsletter covers an unrelated Bitcoin privacy protocol proposal and CFTC guidance on prediction "mention markets."

galaxy.comarticleAdded 8 Oct 2026🧠 AI

Cisco Talos' CAIRN research classifies a malware archetype called 'A3: AI-Analysis Evasion' — samples that embed natural-language instructions aimed at manipulating LLM-based triage/reverse-engineering pipelines. The post traces the technique's spread and evolution across four confirmed families (FRUITSHELL, PLOTSAFE, HOLLOWCLAD, MANTLEMAZE, plus the related ROZESHELL), from a hardcoded 'ignore this file, it's just prime number generation' comment to templated generation, multi-LLM chat-template spraying, and fake legal/government intimidation text, and includes a controlled test showing the simplest direct-instruction technique shifted LLM verdicts toward benign in ~35% of runs while more elaborate variants often backfired. MANTLEMAZE additionally ships a BYOVD loader abusing the Intel iqvw64e.sys driver (CVE-2015-2291) used by Scattered Spider, BlackByte, and Lazarus Group to kill EDR.

blog.talosintelligence.comarticlePublished and added 8 Oct 2026🛡️ Security

Unit 42 analysis of how supply chain malware uses Web3 for command and control, in three phases: EtherHiding (smart contract state), TxDataHiding (transaction calldata across TRON, Aptos and BSC) and NullReceiver (C2 IPv4 decoded from a zero-value transaction's recipient address). It covers the ChainDrop npm worm, the PolinRider campaign and DPRK-linked Axios, Mastra and arrayref compromises. It ends with detection and CI/CD policy guidance.

unit42.paloaltonetworks.comarticleAdded 30 Oct 2026, published 7 Oct 2026🛡️ Security

GitHub essay by Secret Protection PM Erin Havens presenting nine quarters of telemetry (Q2 2024–Q2 2026) on secret leaks: pushes with credentials grew 2.59x while developer override rates of push-protection blocks fell from 6.63% to 3.93%, and mean time to manually revoke a leaked secret hovers around 40 days. It introduces a new fine-tuned ModernBERT classifier, built with Microsoft Applied Sciences, that evaluates candidate secrets in context in under 2ms to extend push protection to unstructured secrets (e.g. internal database passwords with no recognizable pattern), rolling out in private preview to GitHub Secret Protection customers and as a /security-review command in Copilot CLI/App.

github.blogarticlePublished and added 7 Oct 2026🛡️ Security

Snyk benchmarks its Evo Continuous Offensive Security (COS) agent against Claude Security running Mythos on TaintedPort, a public deliberately vulnerable web app with 57 known vulnerabilities and 15 known exploit chains. Evo COS, run gray-box against the live URL plus source, confirmed 10 of 15 exploit chains with runnable proofs of concept — for example chaining an SSRF flaw with a hardcoded JWT signing secret into full admin account takeover — while Claude Security, reasoning over source code alone (white-box), found one additional critical bug but could not prove the vulnerabilities were actually reachable and chainable at runtime. The post argues that proving exploitability requires exercising the live application, not just reading code, and frames SAST-style code review and DAST-style live attack as complementary.

snyk.ioarticlePublished and added 7 Oct 2026🛡️ Security

Google describes a series of registry-level hijacks affecting the .gh (Ghana), .sl (Sierra Leone), and .as (American Samoa) ccTLDs, in which attackers modified authoritative DNS records to obtain unauthorized HTTPS certificates for Google domains and, via Certificate Transparency monitoring, several other major organizations. Chrome mitigated impact by blocking the fraudulent certificates through CRLSets and coordinating revocation with issuing CAs, then urges domain owners to continuously monitor CT logs and publish restrictive CAA records with ACME account bindings, since cached domain-control-validation state can let attackers mint new certs even after DNS control is restored.

blog.googlearticleAdded 7 Oct 2026, published 6 Oct 2026🛡️ Security

Snyk argues AI coding agents reliably write broken access control (BOLA/IDOR, OWASP's top category since 2021) because the facts needed to add an ownership check — what an object belongs to, who may access it, where tenant boundaries sit — are tacit product knowledge that exists nowhere in the code or prompt an agent sees. It explains why SAST tools catch patterned sub-categories like path traversal or SSRF but structurally cannot catch CWE-639/862/863 (missing or incorrect authorization), since there's no bad pattern to match, and proposes reasoning over an assembled "application-context graph" of architecture, data flows and trust boundaries instead. It closes with a five-step team checklist (inventory ID-accepting endpoints, document ownership rules, add authorization-specific PR review, write cross-tenant tests, run deep contextual analysis) and pitches Snyk's Evo Agentic AppSec as the tool built around that approach.

snyk.ioarticlePublished and added 1 Oct 2026🧠 AI

Snyk explains why AI coding agents reliably ship broken object-level authorization (BOLA/IDOR) bugs: the ownership rule that would prevent them (e.g. "invoices belong to organizations") lives in the product's data model and team knowledge, not in the prompt or surrounding code, so the agent produces code that is correct for the stated task but lets any authenticated user access other tenants' objects. The piece maps the flaw to CWE-639/862/863, contrasts it with pattern-matchable classes like SSRF and path traversal that SAST handles well, and lays out five concrete team actions (endpoint inventory, documented ownership rules, explicit authz review questions, per-resource cross-tenant tests, and periodic deep contextual analysis), while pitching Snyk's "application-context graph" and Evo Agentic AppSec as the tool for the pattern-less gap.

snyk.ioarticlePublished and added 1 Oct 2026🛡️ Security

SynthID Bio is Google DeepMind's watermarking technique extended from digital media into synthetic biology, embedding an imperceptible, verifiable signature into AI-designed protein sequences (via a modified ProteinMPNN alongside AlphaProteo) and 3D structures (via a fine-tuned AlphaFold 3 diffusion network) without compromising biological function. Wet-lab tests on protein binders against VEGF-A, SARS-CoV-2 spike RBD, and PD-L1 matched hit rate and binding affinity of unwatermarked designs, and the approach was also extended experimentally to watermark an Evo 2-designed bacteriophage genome with Stanford's Hie lab and Arc Institute. The work targets biosecurity gaps in DNA synthesis screening and public sequence databases (Protein Data Bank, UniProt, GenBank), with DeepMind open-sourcing code, in vitro data, and model weights alongside a methods paper.

deepmind.googlearticlePublished and added 30 Sep 2026🧠 AI

The Hacker News details the "Mini Shai-Hulud" campaign by threat actor TeamPCP, which compromised npm and PyPI packages from TanStack, UiPath, Mistral AI, OpenSearch and Guardrails AI via a chained GitHub Actions attack (pull_request_target abuse, cache poisoning, OIDC token extraction), now tracked as CVE-2026-45321 (CVSS 9.6). The worm mints npm publish tokens directly from stolen OIDC credentials to self-propagate — the first documented case of a worm producing validly SLSA Build Level 3-attested malicious packages — and deploys an obfuscated credential stealer with IDE persistence hooks, a GitHub Actions secret-exfiltration workflow, and a dead-man's-switch that runs "rm -rf" if its rogue npm token is revoked. Over 170 packages and 400+ attacker-controlled repos have been identified across npm and PyPI, with findings credited to Aikido Security, Endor Labs, SafeDep, Socket, StepSecurity, Snyk, Wiz and Microsoft.

thehackernews.comarticleAdded 26 Sep 2026🛡️ Security

A Snyk blog post arguing that vulnerability backlogs traditionally managed as "accepted technical debt" have become genuine attack surface, because AI-accelerated code generation has pushed vulnerability inflow to roughly six new findings per one remediated, unauthored AI-written code removes the "ask the author" triage shortcut, and cheap automated reconnaissance lets attackers walk large backlogs an analyst never would. It illustrates how individually-low-severity findings (an IDOR leaking an internal object ID, a verbose error confirming valid IDs, and an outdated deserialization library) can chain into an authenticated RCE path invisible to severity-based sorting, and argues better prioritization only reorders a backlog rather than shrinking it. It closes with four metrics programs should measure (90-day inflow vs. closure, age of risk-accepted findings, share of human-authored merges, and security-fix merge rate) before promoting Snyk's Evo product.

snyk.ioarticlePublished and added 24 Sep 2026🛡️ Security

Latent Space interview with Eric Nguyen, co-founder/CEO of Radical Numerics, on building genomic language models (GLMs) like Evo and Evo 2 at Arc Institute/Stanford, which use long-context architectures (StripedHyena) to model DNA sequences up to millions of tokens long. The piece covers how these models generalize from DNA to RNA/protein "languages," demonstrate a DNA analog of chain-of-thought by extrapolating aptamer scores beyond training data, and were used by a separate team to generate synthesized bacteriophage genomes — framing biosecurity as an AI capability arms race where the same models raise biological risk and enable defense.

latent.spacearticleAdded 29 Sep 2026, published 23 Sep 2026🧠 AI

Socket's one-year retrospective on the Shai-Hulud npm supply-chain worm, from the September 2025 @ctrl/tinycolor compromise through the November 2025 "Second Coming" wave, the May 2026 public release of the worm's source by TeamPCP, the "Mini Shai-Hulud" OIDC-token-hijacking wave that hit TanStack and Mistral AI, and the August 2026 arrest of two alleged TeamPCP members by Australian Federal Police working with the FBI. It notes Google ran an undercover analyst inside TeamPCP to get stolen credentials revoked, and stresses that the original September 2025 worm authors remain unidentified despite the arrests.

socket.devarticleAdded 21 Sep 2026, published 18 Sep 2026🛡️ Security

Betterleaks is a new open-source secrets scanner built by Gitleaks' original creator (now Head of Secrets Scanning at Aikido) as a drop-in replacement for Gitleaks. It adds CEL-based rule validation, a BPE-tokenization "token efficiency" filter that hits 98.6% recall on the CredData benchmark versus 70.4% for entropy-based detection, default double/triple-encoding handling, parallelized git repo scanning, and a pure-Go (no CGO/Hyperscan) implementation, with v2 plans for auto-revocation, permissions mapping, and LLM-assisted classification.

aikido.devarticleAdded 18 Sep 2026🛡️ Security

Wiz describes an AI detection engine that analyzes model input/output telemetry (prompts, system prompts, tool calls, reasoning) rather than just outputs, in order to catch shifts in AI agent intent such as indirect prompt injection. It walks through OpenAI's disclosed Hugging Face/ExploitGym incident and an internal support-agent phishing-relay scenario, then describes a staged pipeline (regex/SLM candidation, light LLM filtering, deep LLM analysis, correlation with cloud/runtime telemetry) validated against a benchmark of 100+ simulated scenarios covering 57 injected attacks and 45 benign workflows across CI/CD, DevOps, data analyst, support, CLI, and cloud auditor agent personas.

wiz.ioarticlePublished and added 17 Sep 2026🛡️ Security

IBM Research's ALTK-Evolve blog post introduces "consistency guidelines," built on a new diagnostic called the Consistency Analyzer, which resamples an agent's own recorded trajectory to find flip-prone decision points without needing ground truth or a live replay. On AppWorld with a GPT-4.1 ReAct agent, they show a 24.4-point gap between Mean@5 (77.4%) and Pass^5 (53.0% — success on all 5 repeated runs), and demonstrate that injecting the generated guidelines halves that gap to 12.0pp while preserving or improving average accuracy, with gains that generalize to similar tasks and to a weaker model (gpt-oss-120b). The post argues Pass^k should be reported alongside Mean@k as a distinct, orthogonal measure of agent reliability, and links an open-source repo and arXiv technical report.

huggingface.coarticleAdded 29 Sep 2026, published 15 Sep 2026🧠 AI

tl;dr sec issue #345 is a security newsletter digest. It covers Greptile's test showing models miss bugs in their own code, an OCaml cohttp path traversal fix probed within ten minutes of the PR, and a Wiz Version Control DFIR poster for GitHub, GitLab, Bitbucket and Azure DevOps. It also covers an arXiv paper on open-weight agentic worms (61.8% infection of a 33-host testbed) and Endor Labs' 14 flaws in seven AI orchestration platforms.

tldrsec.comarticleAdded 30 Oct 2026, published 10 Sep 2026🛡️ Security

Nathan Lambert argues that unlike past industrial revolutions which delivered tangible goods to average people quickly, AI's benefits remain indirect and concentrated among knowledge workers, risking a repeat of 'Engels' pause' — the 1790-1840 period where UK GDP grew rapidly while working-class wages stagnated. He frames this as a political liability for the AI industry (OpenAI, Anthropic, etc.), predicting a 50-year diffusion arc where infrastructure built today compounds slowly, and suggests robotics/self-driving may eventually deliver the tangible impact LLMs currently lack.

interconnects.aiarticleAdded 29 Sep 2026, published 9 Sep 2026🧠 AI

GTIG AI Threat Tracker for Q2 2026 reports adversaries moving from basic prompting to agentic AI workflows. Cases include a cloud-hosted multi-agent credential harvesting campaign built in under six hours, the "Recon" framework holding over 23,800 stolen secrets, and UNC6780 (TeamPCP) supply chain attacks on PyPI, npm and Docker Hub with prompt injection aimed at LLM scanners. It also covers theft of proprietary AI models, LLMJacking, and Gemini misuse by PRC, Iranian, Russian and DPRK groups.

cloud.google.comarticleAdded 29 Oct 2026, published 8 Sep 2026🛡️ Security

Endor Labs breaks down why AI coding assistants (Claude Code, Cursor, etc.) hardcode and leak secrets (CWE-798): they learn the habit from public training data, then compound it by ingesting whole workspaces including .env files and copying live tokens into new code or MCP configs. It cites hard data — GitGuardian's 2026 report found 28.65M new hardcoded secrets on public GitHub in 2025 and a 3.2% secret-leak rate on Claude Code-assisted commits vs 1.5% baseline, Lakera found credentials in 33 .claude/settings.local.json files across 30 packages, and Wiz found AI-related secrets among the most common validated leaked credential types — then lays out a layered defense (pre-commit/IDE/CI/CD/full git-history scanning, active credential validation, secure prompting) and an incident-response order of operations (rotate, investigate, purge history, revoke, re-scan).

endorlabs.comarticleAdded 3 Sep 2026, published 2 Sep 2026🛡️ Security

Huntress blog post clarifying that DoD's July 13 "strategic pause" only suspended CMMC Phase 2 third-party certification requirements (for solicitations after Nov 2026), while Phase 1 self-assessments, SPRS scoring, and DFARS 252.204-7012's 72-hour CUI incident reporting remain fully in force and now face closer DIBCAC/DOJ False Claims Act scrutiny. It also flags the FAR Council's June 23 proposed CUI rule (part of the Revolutionary FAR Overhaul), which would extend 72-hour breach reporting and a NIST 800-171 Rev 3 baseline to all FAR-based federal contractors, not just the defense industrial base, creating a temporary split between CMMC's Rev 2 and the FAR's Rev 3. It closes with a breakdown of 32 CFR 170.21's strict POA&M limits (no POA&M at Level 1, minimum 88/110 score and only 1-point requirements eligible at Level 2) and practical questions MSPs should ask clients about federal contract exposure.

huntress.comarticleAdded 8 Sep 2026, published 2 Sep 2026🛡️ Security

JFrog vendor post arguing that agentic development (ADLC) introduces new unvetted supply chains — models, MCP servers, skills/plugins, hooks, and APM packages — that bypass traditional signature-based scanning. It cites real incidents: a malicious MCP server impersonating Postmark's email MCP that BCC'd all agent-sent emails to an attacker, and the 'omnicogg' malicious Claude/agent skill that hid a 22MB encoded payload and evaded all 65 VirusTotal engines for 5,000+ installs, plus references to 2026 supply-chain attacks on LiteLLM, TanStack, and Mistral AI. It then pitches JFrog AI Catalog's expanded MCP/skill/model registries as the fix.

jfrog.comarticleAdded 3 Sep 2026, published 2 Sep 2026🛡️ Security

Wiz describes the evolution of its public bucket scanner into an AI-powered "context engine" for data security posture management (DSPM): a multi-agent pipeline where lightweight models triage files and larger models perform deep content analysis, iteratively learning bucket-specific patterns to find sensitive data that regex-based scanners miss. The production system adds structured severity scoring, synthetic/test-data filtering, algorithmic file clustering for scale, and now powers classification across cloud storage, cloud drives, endpoints, and Wiz's Red Agent attack-simulation findings. A one-week scan of public buckets using the engine surfaced over 2,700 sensitive data findings, including correlated credential/schema/export file sets that regex tools would treat as unrelated.

wiz.ioarticleAdded 3 Sep 2026, published 27 Aug 2026🛡️ Security

Wiz CIRT published a DFIR cheatsheet/poster covering the four most common version control platforms (GitHub, GitLab, Bitbucket Cloud/Data Center, Azure DevOps), detailing available log sources, default retention limits (e.g. GitHub's 7-day Git read/write event retention, GitLab not storing Git operations by default), a pre-incident configuration checklist (enabling source-IP metadata, extending retention, log streaming), and a MITRE ATT&CK-mapped matrix of platform-specific audit event names to hunt for during investigations. It illustrates the gaps with a real incident where a compromised token was used to mass-clone repositories containing plaintext secrets, and shows how the same action (e.g. mass repo cloning) surfaces under different event names per platform (git.clone in GitHub, repository_git_operation in GitLab, RepositoryCloneEvent in Bitbucket Data Center).

wiz.ioarticleAdded 3 Sep 2026, published 27 Aug 2026🛡️ Security

StepSecurity analyzes CloudSEK's newly published dataset on TeamPCP, a threat actor that compromised trusted open-source CI/CD components (Trivy GitHub Action, Checkmarx KICS action, telnyx PyPI package, LiteLLM) to harvest 78,330 secrets from 2,186 organizations' CI/CD pipelines across GitHub Actions, GitLab, and Azure DevOps in five days in March 2026. The post breaks down which platforms and credential types were exposed (GitLab led, 230+ Azure DevOps orgs, 157 leaked OpenAI keys) and maps layered CI/CD runtime controls (egress control, runner lockdown, imposter-commit detection, workflow policies) as mitigations against this class of attack.

stepsecurity.ioarticleAdded 3 Sep 2026, published 15 Aug 2026🛡️ Security

Snyk expands on the 'Agent Baseline' (co-authored with Docker and Keycard), a vendor-agnostic reference architecture defining six security outcomes for AI agents — Discover, Constrain, Authorize, Observe, Validate, Respond — and 35 specific controls (e.g. CON-03/04, DIS-04/06/07, AUT-01/02/03, OBS-02, RES-01/02/04, VAL-03/04). The post argues coverage isn't a rollout plan and gives sequencing per use case: developer coding agents should start with sandboxing/capability scoping (Constrain) then discovery, shared internal agents should start with per-principal Authorize controls to avoid confused-deputy failures from shared service accounts, and production agents should prioritize Respond (credential/session revocation, component quarantine, non-agent fallback paths) and outcome validation before finality. It also flags gaps in the current draft (no maturity model, use-case lens not yet in v1.0) and notes the Baseline is open for public comment on GitHub until Sept 30.

snyk.ioarticleAdded 3 Sep 2026, published 12 Aug 2026🛡️ Security

Snyk describes a real customer engagement using its Evo Continuous Offensive Security (autonomous AI pentesting) product against a multi-tenant enterprise SaaS with hundreds of microservices behind an SPA. It details two exploitable findings: a mass assignment bug combined with broken function-level authorization (BFLA) enabling tenant-wide compromise, and a CORS origin-reflection misconfiguration, both validated as reproducible exploits.

snyk.ioarticleAdded 3 Sep 2026, published 10 Aug 2026🛡️ Security

Manifold Security identified 77 malicious "evil twin" extensions uploaded to Open VSX between July 26 and August 1, 2026, that impersonate real Microsoft VS Code Marketplace extensions by reusing their names/namespaces/descriptions under unrelated publisher accounts at low version numbers (e.g. 0.0.1). 58 lightweight variants exfiltrate just the hostname while 19 "recon" variants collect detailed machine, Git repository, CI environment (GITHUB_REPOSITORY, CI_PROJECT_PATH, Azure DevOps, Buildkite, CircleCI, Codespaces, Gitpod), installed-extension, and telemetry opt-out data to mangorbit[.]com, with DNS TXT-based fallback C2 and a persistent multi-day retry schedule. The article also covers the concurrent ChainDrop campaign compromising 450 npm packages (2,244 artifacts) via a Mini Shai-Hulud self-propagating credential-stealing worm using a Bun runtime payload and preinstall hooks, which plants persistence via .claude and .vscode config injection.

thehackernews.comarticlePublished and added 8 Aug 2026🛡️ Security

Cloudflare explains the MCP 2026-07-28 specification, which removes the mandatory stateful session handshake (Mcp-Session-Id) from the core protocol so MCP servers can run as ordinary stateless HTTP workloads (e.g. a single Cloudflare Worker) instead of requiring sticky sessions or Durable Objects. It covers the new Multi Round-Trip Requests (MRTR) model replacing stream-based elicitation, new Mcp-Method/Mcp-Name HTTP headers for gateway-level routing and caching, tightened authorization (CIMD preferred over DCR, RFC 9207 issuer checks, RFC 8707 audience binding), a formal Active/Deprecated/Removed feature lifecycle, and the createMcpHandler API graduating into the official TypeScript SDK, with testimonials from Sentry, Linear, and Anthropic's MCP lead.

blog.cloudflare.comarticleAdded 2 Oct 2026, published 6 Aug 2026🧠 AI

Adversa AI's monthly MCP security digest for August 2026, grouping ten resources: the July 28 MCP specification revision that hardens authorization (RFC 9207 issuer validation, deprecation of Dynamic Client Registration, a stateless core with header-based routing), a confused-deputy indirect prompt injection against Microsoft's Azure DevOps MCP server that hijacks a review agent into exfiltrating wiki data, SANS ISC telemetry showing 49 source IPs scanning for exposed MCP servers and agent credentials in two weeks, and new research (ChainWatch's kill-chain detection via Hidden Markov Models, SPELLSMITH's description-layer mitigations for taint-style flaws, MTGuard's static/dynamic tool-call analysis, and a 33-vulnerability taxonomy of agentic commerce platforms with the AIP-Bench benchmark). It closes with concrete upgrade guidance: audit DCR dependencies, validate issuers per RFC 9207, grep logs for MCP scanning indicators, and stand up a policy-enforcement gateway.

adversa.aiarticleAdded 7 Oct 2026, published 6 Aug 2026🛡️ Security

IBM Research extends K-Search, an evolutionary GPU kernel optimization framework from UC Berkeley Sky Lab that uses an LLM to iteratively propose, compile, and benchmark candidate kernels, with a new MLX backend for Apple Silicon and a structured CUDA-to-MLX translation layer. The translation layer maps CUDA primitives (shared memory, warp reductions, syncthreads) to Metal/MLX equivalents with hardware-specific constraints, letting the search reuse NVIDIA kernel expertise instead of rediscovering optimizations from scratch. Using Gemini 3.5 Pro Preview as both reasoner and code generator, the approach reaches 0.97x the speed of Apple's native MLX attention kernel and delivers up to 20x faster prefill than the community mlx-lm Mamba SSM implementation.

bair.berkeley.eduarticleAdded 29 Sep 2026, published 29 Jul 2026🧠 AI

Snyk explains AI pentesting as an orchestrated system — a reasoning model that plans reconnaissance/exploitation, deterministic DAST tooling for known vulnerability classes, an independent validator model that confirms exploitability, and context from existing scanner findings — designed to catch context-dependent flaws like BOLA/IDOR, cross-tenant leakage, and chained business-logic exploits that signature-based scanners miss. It cites concrete reliability data (frontier models solving only ~26% of hard system-exploitation benchmark tasks, ~30% hallucinated findings without independent validation, 210% YoY growth in valid AI-generated HackerOne reports and 540% growth in prompt-injection reports) and positions Snyk's Evo Continuous Offensive Security product against these evaluation criteria. It also references a RAND 2026 study on low-cost CTF-solving coding agents, Anthropic/Mozilla open-source vulnerability discovery work, and Google GTIG's report of the first in-the-wild AI-assisted zero-day.

snyk.ioarticleAdded 3 Sep 2026, published 27 Jul 2026🛡️ Security

Google DeepMind and Isomorphic Labs describe their joint bioresilience program, organized around preventing misuse of models like Gemini, detecting outbreaks earlier, and accelerating response. Concrete efforts named include a four-step safety process (threat modeling, evaluations, mitigations, monitoring) under DeepMind's Frontier Safety Framework, adapting SynthID watermarking to flag AI-generated biological sequences for DNA synthesis screening, using the AlphaEvolve agent to optimize metagenomic sequencing algorithms for cheaper pathogen surveillance, and applying AlphaGenome and Protein Function annotation to pathogen characterization, alongside Isomorphic Labs' Drug Design Engine (IsoDDE) for rapid countermeasure design.

deepmind.googlearticleAdded 29 Sep 2026, published 16 Jul 2026🧠 AI

Lilian Weng's long-form post argues that the "harness" surrounding a base model — the system that orchestrates planning, tool use, context, memory and evaluation — is as important to recursive self-improvement (RSI) as raw model intelligence. It surveys harness design patterns (workflow loops, file-system-as-memory, sub-agents) and traces an optimization progression from prompts to context engineering (ACE, Meta Context Engineering) to workflow search (ADAS, AFlow) to self-editing harness code (STOP, Self-Harness, Agentic Harness Engineering, Darwin Gödel Machine, Hyperagents) and evolutionary program search (AlphaEvolve, ShinkaEvolve). It closes with open problems for auto-research and self-improving agents: weak evaluators, memory/context lifecycle, negative-result bias, diversity collapse, reward hacking, and the durable need for human oversight, plus a benchmark appendix (PaperBench, CORE-Bench, RE-Bench, MLE-bench, KernelBench). Note: the fetched text is truncated partway through the references/appendix.

lilianweng.github.ioarticleAdded 29 Sep 2026, published 4 Jul 2026🧠 AI

Aikido Security breaks down GitHub's newly shipped self-service credential revocation for Enterprise, which lets org owners bulk-revoke PATs, SSH keys, and OAuth tokens for compromised accounts in one action instead of hunting down individual tokens. The piece ties the feature's timing to a string of 2026 incidents caused by incomplete credential rotation: the Trivy GitHub Actions compromise that force-pushed 75 malicious version tags and cascaded into Checkmarx, and Microsoft's durabletask package/repo being repeatedly compromised via the same never-fully-rotated account (Miasma worm). It also explains why atomic rotation is infeasible at scale and recommends pinning GitHub Actions to commit SHAs instead of tags.

aikido.devarticleAdded 3 Sep 2026, published 1 Jul 2026🛡️ Security

Huntress details ConsentFix, an evolution of ClickFix that abuses Microsoft 365 OAuth sign-in flows: victims are phished via password-protected Dropbox or DocSend lures, shown a fake Microsoft sign-in page, and tricked into dragging a localhost callback link into their browser, which exfiltrates OAuth tokens and hijacks the session without needing a password or triggering MFA. A cybercrime forum post published the full technique with working code and infrastructure such as Cloudflare Pages, workers.dev, and Pipedream webhooks, and showed attackers using LinkedIn, ZoomInfo, and Hunter.io to profile victims before sending lures.

huntress.comarticleAdded 3 Sep 2026, published 29 Jun 2026🛡️ Security

Cloud Security Alliance research note arguing that traditional vulnerability management (scan, ticket, patch on a calendar) is breaking under AI-driven vulnerability discovery volume, NVD's April 15, 2026 risk-based triage policy that limits full CVE enrichment to CISA KEV/EO 14028/federal-use software, and compressed disclosure-to-exploitation windows. It defines VulnOps as a flow-oriented operating discipline (borrowing SRE/DevOps metrics like lead time, change-failure rate, and pipeline saturation) built on continuous discovery, EPSS/KEV-based risk prioritization instead of CVSS-only ranking, automated remediation-as-code, and first-class SBOM/supply-chain visibility, while also flagging agentic AI itself (prompt injection, tool-poisoning, MCP command execution) as a new vulnerability class the practice must cover.

labs.cloudsecurityalliance.orgarticleAdded 3 Sep 2026, published 13 May 2026🛡️ Security

Huntress and Microsoft detail EvilTokens, a phishing-as-a-service (PhaaS) platform sold on Telegram for ~$1,500 that automates OAuth device code phishing to steal valid session tokens and bypass MFA entirely, relaying attacks through the Railway PaaS. The kit integrates AI to generate role-specific, contextually accurate lures, dynamically generate device codes to remove timing constraints, and automatically draft follow-on wire-fraud emails in the victim's own voice after mailbox compromise — a campaign that hit 344 organizations across five countries in 16 days and evaded Cisco Secure Email, Trend Micro, and Mimecast. The piece also covers sibling PhaaS kits (Tycoon2FA, BlueKit, Kali365) and recommends conditional access restrictions, phishing-resistant FIDO2/passkey MFA, and refresh-token revocation as mitigations.

huntress.comarticleAdded 3 Sep 2026, published 11 May 2026🛡️ Security

Huntress breaks down how modern business email compromise (BEC) campaigns in Google Workspace have evolved from simple invoice fraud into multi-stage identity abuse: attackers use OAuth token theft, password-reset/MFA emails, and mailbox filters to hide alerts, persist via forwarding rules, and pivot laterally into other SaaS platforms. The piece argues traditional content-based email detection misses these campaigns and that defenders need identity-centric monitoring (token lifecycle, OAuth consent anomalies, mailbox config changes) — framing this as the rationale for Huntress's expansion of managed identity threat detection (ITDR) into Google Workspace.

huntress.comarticleAdded 3 Sep 2026, published 5 Mar 2026🛡️ Security

Huntress's 2026 threat-landscape overview argues Linux is closing the threat gap with Windows, citing rapid mass exploitation of the React2Shell vulnerability (leading to PeerBlight malware and XMRig cryptomining), growing multi-OS ransomware campaigns hitting Windows/Linux/ESXi simultaneously, and WSL as an emerging attack surface for credential theft and Windows Defender Application Control bypass via Linux ELF binaries. It also covers LLM-assisted vulnerability research (CVE-2025-37899 found via OpenAI's o3) and profiles Linux-targeting threat actors including LockBit 5.0, Akira, Qilin, Gunra, BlackCat/ALPHV, Volt Typhoon (KV-botnet), and Lazarus Group.

huntress.comarticleAdded 3 Sep 2026, published 3 Mar 2026🛡️ Security