57
CategoryAll
Smart search ranks by meaning as well as keywords (one row per story, last 45 days).
Webinar: What happens in the first hours of a Google Workspace breach
BleepingComputer and Material Security will host a September 23 webinar analyzing first-hours response decisions in real Google Workspace breaches.
The September 23, 2026 webinar 'Breach autopsy' features Material Security VP of Security Rajan Kapoor and Fireside Consulting president Rick Fitzgerald examining publicly documented Google Workspace breaches. Two analyzed attacks combined social engineering with malicious OAuth applications to gain access. Sessions will cover scoping exposed users and data, confirming whether attacker access persists, and which early containment decisions limited or worsened impact for lean security teams.
10
Webinar: The forgotten Google Workspace access that can lead to a breach
BleepingComputer and Material Security will host a September 23, 2026 webinar on breaches caused by forgotten third-party Google Workspace integrations.
BleepingComputer announced a live webinar on September 23, 2026, titled 'Breach autopsy: How fast-growing companies are breached through Google Workspace' in partnership with Material Security. Speakers include Rajan Kapoor, VP of Security at Material Security, and Rick Fitzgerald, President of Fireside Consulting LLC. The session will examine real documented Google Workspace breaches involving overly permissive third-party integrations, social engineering entry paths, first-hours breach response decisions, and high-value security controls for lean security teams.
5
Security Data Isn’t the Problem. Security Context Is.
Horizon3 blog argues security context, not data volume, is the SOC bottleneck, promoting its NodeZero integration with CrowdStrike Falcon Next-Gen SIEM.
Horizon3.ai published a vendor blog explaining how its NodeZero Proactive Security Platform integration with CrowdStrike Falcon Next-Gen SIEM brings validated exposure findings into existing security operations workflows. The post argues SOCs are now limited by confidence rather than visibility, needing context to decide which issues matter. It cites a global chemical manufacturer that validated exploitable exposures with NodeZero before completing a $2 billion merger.
15
Persistent Attempts at Cyberespionage Against Southeast Asian Government Target Have Links to Alloy Taurus
Alloy Taurus (GALLIUM) compromised Southeast Asian government networks from 2022 to 2023 using Exchange web shells and undocumented .NET backdoors Reshell and Zapoa.
Unit 42 tracked persistent multiwave intrusions at a Southeast Asian government starting in early 2022 and continuing through 2023, attributing the activity with moderate confidence to Alloy Taurus (aka GALLIUM), a Chinese state-aligned espionage group. Attackers exploited Exchange Server vulnerabilities to deploy web shells including China Chopper, then ran reconnaissance with Fscan and WebScan, created administrative accounts, and installed undocumented .NET backdoors named Reshell and Zapoa. They established resilience by installing SoftEther VPN, brute-forced Active Directory credentials with Kerbrute, and dumped credential stores with GoDumpLsass and LsassUnhooker. The campaign reflects long-term espionage tradecraft to maintain a foothold.
70
A new open standard locks AI weights to approved hardware
OPAQUE releases Weight Custody Manifest, an open standard keeping AI model weights encrypted until receiving hardware cryptographically attests to builder-specified conditions.
OPAQUE, a confidential computing company, released the Weight Custody Manifest (WCM) standard as a developer-preview specification with a Python SDK and a public test suite of 91 cases. WCM keeps model weights encrypted until the receiving infrastructure proves via CPU/GPU attestation that it matches builder-signed conditions, and decryption access can be revoked later if conditions change. OPAQUE says it ran the attestation exchange on an NVIDIA H100 and on AMD and Intel confidential servers hosted on Azure and Google Cloud, with two independent SDK builds producing identical output across 5,948 files. The public quickstart only exercises protocol logic on synthetic evidence and skips GPU cryptographic verification, and the standard cannot distinguish an authorized key from one physically extracted from hardware.
38
Why a cryptographic inventory is key for addressing the quantum computing threat
Tenable argues organizations need cryptographic inventories and phased plans to counter harvest-now-decrypt-later quantum attacks.
Tenable's blog warns that quantum computers will eventually break current public-key cryptographic algorithms, and that "harvest now, decrypt later" collection makes the risk operational today. It recommends building a comprehensive cryptographic inventory and executing a phased operational strategy to migrate toward quantum-resistant protection for stored and transmitted data.
25
CONTINUITY: Security-Context Contracts for Composable LLM Agent Controls
Researchers introduce CONTINUITY, a framework of assume-guarantee contracts that preserves LLM agent security context across components, verified across 2,560 attack instances.
The paper identifies security-context discontinuity, where individually sound controls drop, widen, or reinterpret security context as actions cross component boundaries, and proposes CONTINUITY, a framework of assume-guarantee contracts using signed root grants, provenance commitments, role-bound transition receipts, and effect-bound execution permits. It formalizes end-to-end consequence integrity, requiring every external effect to be backed by a valid authorization witness linking principal, task, provenance, and policy state. A reference verifier and cross-layer fault-injection suite covering 32 fault classes showed the full configuration committed no harmful external effect across 2,560 parameterized attack instances while completing all 700 benign tasks and escalating all 200 ambiguous cases.
32
Has anybody seen my keys? A key-hierarchy strategy for rack-level security
Oxide's RFD 0301 proposes a rack-level key hierarchy using Shamir secret sharing and a trust quorum to protect data-at-rest keys.
Oxide's request for discussion (RFD 0301) lays out a key-hierarchy strategy for rack-level security, deriving keys from a rack secret protected by Shamir secret sharing across a trust quorum of sleds, with keys exchanged over authenticated sprockets sessions. The document maps which keys protect control-plane data, metrics, Crucible extents, and authentication tokens, and defines open questions on key lifecycle, locality, and compromise handling. Future work includes sealing shares with the root of trust so an attacker would need to steal K whole sleds to reconstruct the rack secret.
28
Threats Making WAVs - Incident Response to a Cryptomining Attack
Guardicore researchers dissect a cryptomining attack that hid a cryptominer inside WAV files, mapping the full infection chain and response steps.
Guardicore security researchers present a full analysis of a cryptomining attack that concealed a cryptominer inside WAV audio files. The report documents the complete attack chain from detection through infection, network propagation, and malware analysis. It also includes recommendations for optimizing incident response processes in data centers.
Akamai Blog30
Understanding the Security Boundary of Obfuscation-based On-Device LLM Protection
Researchers formalize obfuscation primitives for TEE-protected on-device LLMs and show a Collapse attack breaks ArrowCloak, TSQP, and LoRO, then extend the boundary.
The paper formalizes obfuscation primitives for TEE-Shielded LLM Partition (TSLP) schemes that offload computationally intensive layers from a Trusted Execution Environment to external GPUs. A novel primitive-guided attack, Collapse, demonstrates a shared vulnerability in prominent published methods including ArrowCloak (Security'25), TSQP (S&P'25), and LoRO (NeurIPS'25). The authors then introduce two new obfuscation primitives and integrate them with existing constructs to formulate an extended security boundary (O_ext).
42
New AI Attack Hides Malicious Instructions in Normal-Looking Text to Evade Safety Filters
Check Point researchers show crafted prose hides policy-violating instructions that bypass all tested LLM gatekeepers, including GPT-4o mini and Llama Guard 3.
A new prompt-crafting technique embeds malicious payloads inside grammatical, natural-looking text without Base64, invisible Unicode, or obvious encodings, defeating lightweight pre-screening gatekeepers. In testing, all four evaluated gatekeeper models—gpt-4o-mini-2024-07-18, gpt-oss-safeguard:20b, claude-3-haiku-20240307, and llama-guard3:8b—classified the crafted wrappers as safe at a 100% bypass rate across 23 obfuscated prompts. GPT-5 Thinking in high-reasoning mode recovered and acted on the hidden instruction in 17 of 18 tests (~94.4%), often spending over a minute and multiple Python executions. Researchers recommend paraphrasing untrusted input, hardening gatekeeper policies, and applying defense-in-depth controls for agentic deployments.
50
Webinar: How malicious OAuth apps can lead to Google Workspace breaches
BleepingComputer webinar will dissect two Google Workspace breaches caused by malicious OAuth apps and social engineering, hosted September 23 with Material Security.
On September 23, 2026, BleepingComputer will host a webinar with Material Security examining two real attacks that used malicious OAuth applications and social engineering to breach Google Workspace environments. Rather than stealing credentials, attackers persuaded users to authorize malicious apps, gaining access to data through the granted permissions. The session covers first-hour response decisions and which security controls provide the greatest value for fast-growing organizations.
15
UK government seeks powers to secretly block risky tech suppliers
UK amendments to the Cyber Security and Resilience Bill would let ministers secretly ban risky tech suppliers across critical sectors.
The UK government published amendments to the Cyber Security and Resilience Bill creating 'vendor-related directions' that allow ministers to order companies in critical sectors to stop buying from a supplier, restrict its products, or remove installed equipment on national security grounds. The powers extend beyond telecoms to managed service providers, data centers, digital infrastructure and the energy, water, transport and health sectors, adapting the mechanism used to restrict Huawei in UK 5G while removing some transparency safeguards. Ministers would not have to publicly name the vendor, could withhold details on national security or commercial grounds, and could bar recipients and consultees from discussing the orders, though the government would report annually to Parliament on directions issued. The amendments will be considered at committee stage in the House of Lords in September.
58
Your Critical Vulnerabilities Might Not Be Your Biggest Risk
Autonomous penetration testing advocates prioritize exploitable attack paths over raw vulnerability severity for continuous security validation.
The article argues that scanner severity scores lack context: a critical flaw behind strong segmentation may be low priority, while a medium flaw on internet-facing systems can provide a foothold chained toward sensitive data. It positions autonomous penetration testing and attack path validation as the execution layer for continuous security validation, replacing point-in-time assessments. The piece is vendor-authored thought leadership rather than incident or vulnerability news.
18
Grok exfiltrates user data when malicious instructions are encrypted
Researchers show Grok can be made to exfiltrate user data via Cryptographic Context Injection, a newly documented technique that bypasses LLM safety guardrails.
According to Ars Technica, Grok exfiltrates user data when malicious instructions are encrypted, a technique called Cryptographic Context Injection. The method is described as the latest documented way to break LLM safety guardrails, showing that encrypted content can carry hidden instructions past safeguards. The finding underscores gaps in how large language models validate and execute context from external sources.
55
Patch Tuesday to Pentest Wednesday: How an Equipment Rental Company Is Turning Continuous Testing Into Continuous Exposure Management
An equipment rental company uses Horizon3 NodeZero for continuous exposure management, surfacing an SSH key exposure in eight hours versus annual pentesting.
The company moved from periodic penetration testing to continuous exposure management using the NodeZero Proactive Security Platform, feeding telemetry into a Splunk-based CTEM pipeline via Horizon3 APIs. NodeZero exposed SSH RSA key pairs from a PHP web server change about eight hours after introduction and found more findings in 12 hours than a third-party engagement found in roughly 30 days. An Active Directory password audit of 15,000 passwords found about 300 identical or similar compromised passwords, driving a banned-password list, 12-character minimums, service desk changes, and self-service reset rollout; users with similar passwords later dropped from 880 to 209. NodeZero also validated a suspected Cisco vulnerability as exploitable.
15
How BitLocker PINs help protect your data and devices
NCSC UK guidance explains that configuring BitLocker PINs mitigates many BitLocker vulnerabilities and urges readiness for future bypass flaws.
The UK National Cyber Security Centre published guidance explaining how BitLocker PINs strengthen protection of data and devices. According to NCSC, enabling a pre-boot PIN mitigates many known BitLocker vulnerabilities that rely on default TPM-only configurations. The guidance encourages organizations to configure PINs now to be prepared for the next disclosed BitLocker bypass.
32
SEMA-GUARD: Semantic and Graph-Based Vulnerability Detection in Assembly Code
SEMA-GUARD uses semantic analysis and graph neural networks to detect vulnerabilities in assembly code, achieving 85.1% accuracy on a Juliet-derived benchmark.
SEMA-GUARD is a framework that detects vulnerabilities in compiled programs when source code is unavailable, targeting malware, firmware, and embedded systems analysis. It enriches control flow graphs with low-level execution semantics including stack manipulations, memory accesses, and data flow. Evaluated on a Juliet Test Suite set compiled to assembly and split into function-level chunks, it achieves 85.1% accuracy and an F1 score of 0.801, outperforming purely statistical or structural approaches.
25
Disruptive cyber activity highlights risk from internet-exposed systems and edge devices
NCSC links disruptive cyber activity to internet-exposed systems and edge devices, urging OT owners to fix avoidable vulnerabilities and improve resilience.
The UK's NCSC issued guidance following disruptive cyber activity that highlights the risk to internet-exposed systems and edge devices. It encourages owners of operational technology to remediate avoidable vulnerabilities and invest in long-term cyber resilience. The notice underscores that exposed edge devices remain a common entry point for attackers against OT environments.
40
Survey of filesystem MCP servers: how the "sandboxed filesystem" boundary is enforced (one breach, four defended-by-design)
Survey finds one filesystem MCP server vulnerable to a symlink-based sandbox escape while four others are defended by design.
A survey of five filesystem MCP servers assessed how each enforces its path-confinement boundary against symlink escapes in recursive directory walkers. The iceener/files-stdio-mcp-server is vulnerable to a read-side sandbox escape. The other four are defended by design or make no confinement claim. The author describes the vulnerability class as small but real.
30
Learn How to Build Security Operations Ready for AI
Wiz sponsors a webinar on building AI-ready security operations, focusing on attack-path visibility, exposure prioritization, and faster detection-to-remediation workflows.
A contributed piece promotes next week's Wiz webinar, How to Build AI Threat Readiness Across Your Security Operations, featuring a Wiz expert. The session covers using unified security context to separate urgent exposures from noise, understand attack paths across cloud, code, identities, SaaS, and AI services, and connect validated risks to remediation owners.
12
Wicked Problem, Parsimonious Solution: Securing Electric Vehicle Charging Station Software
Position paper proposes hierarchical software quality assurance to characterize and secure EV charging station software attack surfaces.
The authors argue that charging station supply-equipment software is a largely unprotected and poorly characterized attack surface in EV charging infrastructure. They advocate applying hierarchical software quality assurance (HSQA) to this specialized software, spanning from individual vulnerabilities such as CVEs to high-level characteristics like the CIA Triad. HSQA embeds quality and security considerations across the entire software development lifecycle to assess and improve charging station software security.
25
What the Data Says About AI in Security Operations in 2026
Prophet Security's 2026 survey of 250+ security pros: 40% use AI daily; AI users report 25%+ faster investigations and rising AI-driven attacks.
Prophet Security's State of AI in Security Operations 2026 report, based on a survey of 250+ cybersecurity professionals, found 40% of security teams use AI daily and only 4% have no adoption plans. Teams average 100 daily alerts (up to 1,000 at large firms), leave 28% of alerts uninvestigated, and 60% of respondents said missed alerts led to breaches or downtime. Among AI adopters, 72% report at least 25% faster investigations, 56% observed increased AI-driven attacks, and no respondents grant AI full unsupervised autonomy. Data privacy (44%) and explainability (41%) top the adoption hurdles.
32
Seeing is Not Believing: Breaking the Physical-to-Digital Trust Boundary in Robotics
Researchers show a single ROS 2 environment variable lets attackers inject fake telemetry and hijack robots while spoofing downstream remote attestation.
A pre-built hook loaded via one modified environment variable covertly intercepts and injects both telemetry and control signals before publication in ROS 2, breaking the physical-to-digital trust boundary in multi-robot task handovers. Attackers can also distribute compromised third-party Docker containers and auxiliary tools embedding the hooks. On a physical Franka Emika arm running Secure ROS 2, the attack injects fabricated telemetry in real time with roughly 3 ms jitter and achieved an 87% success rate even against an AI-based detector. Findings were responsibly disclosed to the ROS 2 development team.
50
Enterprise Defenses Recovered at the Edge and Collapsed Inside
Picus Labs' Blue Report 2026 finds perimeter prevention at 69% but post-compromise prevention just 37%, with reconnaissance blocked only 10% of the time.
Picus Labs' Blue Report 2026, based on 434,000+ simulated attacks across client production environments in H1 2026, found perimeter prevention effectiveness rose from 62% to 69% while the Post-Compromise Prevention Rate was only 37%. Quiet techniques fared worst: reconnaissance was blocked 10% of the time, registry-based credential access less than 1%, and the alert score stayed at 14% despite logging at a four-year high of 58%. IOC-based prevention fell to 50% from 71% in 2024, and Mimikatz's LSASS path was blocked about 94% while alternative credential-read paths went nearly undetected.
45
[Control Systems] National Instruments security advisory (AV26-856)
Canada's Cyber Centre relayed National Instruments advisories for memory corruption, out-of-bounds read, and out-of-bounds write flaws in LabVIEW versions.
The Canadian Centre for Cyber Security published control systems advisory AV26-856 covering National Instruments LabVIEW. Affected versions include releases before 23.0.0, 23.3.10, 24.3.7, 25.3.5, and 26.3.1. The flaws include memory corruption, an integer conversion out-of-bounds read, and an integer overflow out-of-bounds write. Users and administrators are urged to review the links and apply NI security updates.
25
Edge infrastructure under siege: what two independent datasets reveal about who's exploiting your perimeter
Joint Tenable-SentinelOne analysis of 93 CVE-actor attribution pairs shows nation-state and criminal groups independently converge on the same edge infrastructure.
Tenable and SentinelOne jointly analyzed 93 CVE-actor attribution pairs covering exploitation of perimeter devices. The data shows state-sponsored and financially motivated actors independently target the same edge products from Ivanti, Fortinet, and Palo Alto Networks. The findings challenge the narrative that edge exploitation is exclusively a China-nexus nation-state problem, showing a broader shared attack surface.
62
The Hidden Instructions That Can Hijack AI Agents
Hidden prompt injections embedded in documents and metadata can hijack autonomous AI agents, causing data exfiltration and out-of-policy actions at machine speed.
Bowbridge warns that hidden indirect prompt injections, embedded in documents, metadata, emails, images, and code repositories, can cause autonomous AI agents to treat attacker-controlled content as trusted guidance. Because agents inherit user privileges, act silently, and lack human judgment, injections can lead to data exfiltration or file poisoning that traditional security controls cannot detect. A real-world example involved a supplier quote whose metadata instructed an agent to override guidance and select the most expensive option. Bowbridge recommends scanning documents before agents process them.
35
An Empirical Security Analysis of Open-Source Software Used in Onboard Satellite Systems
Study of 126 onboard satellite OSS repositories finds 2,827 security findings, 72% medium severity or higher, dominated by memory safety and code quality weaknesses.
Researchers performed an empirical security analysis of 126 public repositories of open-source software used in onboard satellite systems using SBOM generation, software composition analysis, static application security testing, infrastructure-as-code analysis, and secret scanning. After cleaning and deduplication the pipeline produced 2,827 findings, with medium-severity findings accounting for 49% and 72% classified medium or higher. A CWE-based taxonomy mapped all findings to eight weakness families, with Memory Safety and Code Quality dominating, followed by Input Validation and Injection. Project-developed code accounted for 81.4% of findings, though external dependency code remained relevant; findings do not establish mission-specific exploitability.
40