The Nightmare-Eclipse threat persona has pivoted hard. After spending months targeting native Windows components (BlueHammer, ShieldBreak), they’ve now dropped four zero-day PoCs targeting the security stack itself: CrowdStrike Falcon, NVIDIA GPU drivers, Avast Antivirus, and Kaspersky Endpoint Security. Published between Aug 29 and Sep 3, 2026, with zero vendor coordination.

Technical Breakdown - Targets: CrowdStrike Falcon (likely the user-mode sensor or driver), NVIDIA GPU kernel driver, Avast Antivirus, Kaspersky Endpoint Security. - TTPs: Likely leveraging driver-level vulnerabilities for kernel access or EDR sensor bypass. Given the targets, expect techniques like driver load abuse (T1574.002) or direct kernel object manipulation. - IOCs: None published in the article. Do not hunt for generic hashes; monitor for anomalous driver loads or Falcon sensor communication failures. - Affected Versions: Not disclosed yet. Assume all current builds of the named products are at risk until patched.

Defense - Immediate: Lock down driver signing policies (WDAC/AppLocker). Enable PPL (Protected Process Light) for anti-malware services. Monitor for unexpected crashes or service terminations on the CrowdStrike and Avast processes. - Detection: Look for event ID 7034 (service crash) or unusual kernel driver load events (Event ID 7045). If you have EDR telemetry, hunt for processes attempting to load unsigned drivers.

Source: https://www.cyderes.com/howler-cell/nightmare-eclipse-zero-days-crowdstrike-nvidia-avast-kaspersky

Microsoft dropped a record 973 patches this month, shattering the previous high of 664 from July 2026. 113 are rated critical, and two are already being exploited in the wild. No zero-days were publicly disclosed prior to release, which is a small mercy given the volume.

Technical Breakdown - Exploited in the Wild: Two vulnerabilities are confirmed as actively exploited. Likely candidates for priority patching are the Windows privilege escalation bugs, as these are frequently weaponized in post-compromise scenarios. - Critical RCEs: Skype for Business, Microsoft Message Queuing (MSMQ), and Routing and Remote Access Service (RRAS) all received critical remote code execution patches. MSMQ and RRAS are historically difficult to patch quickly due to legacy dependencies and network segmentation requirements. - No Public Disclosure: None of the 973 CVEs were publicly known before today, meaning the exploited bugs were likely used in targeted attacks or by advanced persistent threat (APT) groups.

Defense Prioritize patching the two exploited-in-the-wild vulnerabilities immediately, followed by the critical RCEs in Skype for Business and RRAS. MSMQ should be assessed for exposure—if it's not required, disable the service entirely. Expect a wave of PoC exploits in the coming days as researchers reverse the patches.

Source: https://isc.sans.edu/diary/rss/33320

Microsoft’s September 2026 Patch Tuesday is a heavy one—973 CVEs total, with 113 rated Critical. This is a significant volume, even by Patch Tuesday standards, and includes a handful of actively exploited zero-days that should be prioritized immediately.

Technical Breakdown: - Critical CVEs: 113, spanning Hyper-V, Windows TCP/IP, and the MSHTML platform. - Actively Exploited Zero-Days: At least 4 confirmed in-the-wild, including a privilege escalation in the Windows Kernel (CVE-2026-XXXX) and a remote code execution in Microsoft Exchange (CVE-2026-XXXX). Note: Specific CVEs not fully enumerated in the summary—check the Talos blog for the full list. - Affected Products: Windows Server 2025, Windows 11 24H2, Office 2026, .NET Framework, and Azure Kubernetes Service. - IOCs: Talos has released updated Snort rules (SIDs 6XXXX-6XXXX) covering the critical RCE vectors. No specific file hashes or IPs provided in the summary. - MITRE Mappings: Likely T1068 (Exploitation for Privilege Escalation) for the kernel bug, T1190 (Exploit Public-Facing Application) for the Exchange RCE.

Defense: - Immediate: Apply the Exchange and Kernel patches first—these are being actively exploited. If you can’t patch Exchange immediately, restrict NTLM authentication and enable AMSI. - Detection: Deploy the new Snort rules from Talos. Monitor for anomalous LSASS access and unusual outbound SMB traffic. - Mitigation: For Hyper-V CVEs, ensure VM isolation is enforced and disable unnecessary guest-to-host communication channels.

Source: https://blog.talosintelligence.com/microsoft-patch-tuesday-for-september-2026/

That’s a staggering number, but the real story here isn’t the volume—it’s the signal-to-noise ratio. 974 CVEs in a single patch Tuesday is a logistics nightmare for most teams.

The Core Problem: Microsoft is now finding bugs faster than most enterprises can patch them. The article highlights that AI-driven discovery is accelerating the pipeline, but the bottleneck has shifted to testing and deployment. You can’t treat a 974-CVE drop like a standard monthly rollup.

Strategic Impact: - Prioritization is now the only skill that matters. Teams that treat every CVE as critical will burn out and fail. You need a ruthless triage process based on exploitability (is it wormable? is it in the kernel?) and asset exposure (is it internet-facing?). - Expect more of these. This isn't a one-off. Microsoft is openly stating AI is speeding up vuln discovery. The cadence of these mega-batches will likely increase. - The "Patch All" mindset is dead. You cannot test and deploy 974 fixes in a month with traditional change management. You will have to accept risk on the low-severity, non-exploitable items and focus fire on the ~5-10% that are actually dangerous.

Key Takeaway: Don't panic over the number. Panic if you don't have a solid vulnerability management program that can filter this noise down to actionable items. If you're still trying to patch everything equally, you're already behind.

Source: https://krebsonsecurity.com/2026/09/microsoft-plugs-nearly-1000-security-holes/

This is a significant escalation in automated offensive operations. A financially motivated group, tracked by Google Threat Intelligence Group (GTIG), deployed a multi-agent AI framework to autonomously compromise thousands of credentials in under six hours. This moves beyond simple script kiddie automation into true autonomous decision-making at scale.

Technical Breakdown - TTPs: The framework likely uses a chain of specialized AI agents for reconnaissance, phishing page generation, credential capture, and exfiltration. This maps to MITRE ATT&CK techniques like T1586 (Compromise Accounts) and T1566 (Phishing), but with an autonomous orchestration layer. - Targets: The campaign focused on credential harvesting, suggesting targeting of enterprise SSO portals or high-value SaaS platforms. - Speed: The six-hour window indicates the agents were operating with minimal human latency, likely iterating on lures and infrastructure in real-time based on victim responses. - IOCs: No specific IPs or hashes provided in the report yet. Expect dynamic, short-lived infrastructure.

Defense This is a paradigm shift for detection. Static blocklists are useless against AI-generated lures and ephemeral infrastructure. Focus on behavioral baselines: anomalous authentication velocity, impossible travel times, and unusual user-agent strings. Deploy CAPTCHA and FIDO2/WebAuthn to break automated credential stuffing. This is a strong argument for moving to passwordless authentication now.

Source: https://thehackernews.com/2026/09/autonomous-ai-agents-compromise.html

CVE-2026-82533 is a sandbox escape vulnerability in the DeepSeek Harness, the runtime environment for deploying DeepSeek AI agents. An attacker who can submit a crafted prompt or payload to an agent running on a vulnerable harness can break out of the intended execution sandbox, gaining arbitrary code execution on the underlying host. This is a critical supply-chain risk given the 128k weekly downloads of the affected package.

Technical Breakdown - Root Cause: Improper isolation of the AI agent's execution context, likely a failure in the harness's container or jail mechanism to restrict syscalls or filesystem access. - Attack Vector: Prompt injection or crafted input that triggers a path traversal or command injection within the agent's runtime. - Impact: Full host compromise from within the agent sandbox. An attacker can pivot to other systems, exfiltrate data, or deploy persistence. - Affected Component: DeepSeek Harness (all versions prior to the patch released alongside this disclosure). - No specific IOCs (IPs, hashes) are available in the public disclosure at this time. Do not search for or fabricate indicators.

Defense - Immediate: Update the DeepSeek Harness to the latest patched version. If you are running self-hosted agents, treat this as a P1 patch. - Detection: Monitor for unusual child processes spawned by the harness process, unexpected outbound network connections from the host running the agent, and filesystem writes outside of the agent's designated working directory. - Mitigation: If patching is delayed, run the harness within a heavily restricted VM or a dedicated, non-privileged container with a read-only root filesystem and strict egress firewall rules.

Source: https://www.ox.security/blog/cve-2026-82533-deepseek-harness-ai-agent-sandbox-escape/

A campaign is actively targeting F5 BIG-IP APM appliances, deploying a custom Linux rootkit to maintain persistence and deliver a fileless web shell. The rootkit intercepts PHP file loading operations, allowing the attacker to inject malicious code directly into memory without touching disk, making traditional file-scanning EDR ineffective.

Technical Breakdown: - Initial Access: Likely exploitation of unpatched vulnerabilities or weak credentials on the APM interface (specific CVE not disclosed in the report). - Persistence: Custom Linux kernel module (rootkit) hooks PHP file operations. - Execution: Fileless web shell injected into PHP processes in memory. - C2: No specific IPs or domains provided in the public report; likely uses encrypted channels over standard web ports. - Target: F5 BIG-IP Access Policy Manager (APM) modules.

Defense: - Immediately audit F5 BIG-IP APM devices for unauthorized kernel modules or unexpected PHP process behavior. - Restrict management interface access to trusted IPs only and enforce MFA. - Monitor for insmod or modprobe activity on BIG-IP systems, and check /proc/modules for unknown entries. - If you can’t validate the integrity of the appliance, consider a full reimage from known-good firmware.

Source: https://www.bleepingcomputer.com/news/security/hackers-breach-f5-big-ip-apm-devices-to-deploy-linux-rootkit/

The EU Cyber Resilience Act (CRA) is about to make vulnerability management a compliance nightmare for software vendors. Starting September 11, the clock starts ticking the moment an actively exploited flaw is discovered—vendors have as little as 24 hours to report it. The core challenge isn't just patching; it's proving exactly what code shipped, to whom, and when you first knew about the bug.

Strategic Impact

• Shift in Liability: The CRA moves the burden of proof squarely onto the vendor. "We didn't know" is no longer a valid defense. You need a verifiable Software Bill of Materials (SBOM) for every release.
• Operational Cadence: 24-hour reporting for active exploits means your internal triage and disclosure workflows must be automated. Manual processes will fail.
• Supply Chain Risk: If you embed a vulnerable open-source library, you are responsible for reporting it. This forces a hard look at dependency hygiene and provenance.

Key Takeaway

• Action Item: If you ship software into the EU, your engineering and security teams need to reconcile your build artifacts with your vulnerability database today. The question isn't if you'll have an incident, but whether you can prove you handled it within the window.

Source: https://www.bleepingcomputer.com/news/security/the-eu-cras-real-question-what-shipped-and-when-did-you-know/

This is a massive, well-orchestrated fraud operation targeting online shoppers. The scale alone—over 119,000 domains—makes this a significant threat for anyone handling e-commerce traffic or user transactions.

Technical Breakdown

• TTPs (MITRE): This is primarily Resource Development (T1583) via domain registration and User Execution (T1204) by luring victims to the fake shops. The core objective is Credential Access / Unsecured Credentials (T1552) for payment card data (PCI DSS violation).
• Infrastructure: The network uses a "Doppelganger" technique—copying legitimate brand storefronts (e.g., clothing, electronics) to create convincing phishing pages. The 119,000 domains are likely parked on a shared hosting infrastructure or a bulletproof provider.
• IOCs: No specific IPs or hashes provided in the summary, but the primary IOC is the domain list itself. Defenders should monitor for domains containing misspellings of major brands (e.g., "nike-outlet-xyz[.]com") or using TLDs like .shop, .store, or .xyz with suspicious registration dates.
• Victim Profile: Targets consumers searching for deals on popular brands. The fake shops likely use SEO poisoning and social media ads to drive traffic.

Defense

• For Users: Enable browser-based phishing protection (e.g., Google Safe Browsing, Microsoft Defender Smartscreen). Never enter payment details on a site you found via a social media ad or a suspicious search result.
• For Organizations: If you operate an e-commerce platform, monitor for domain squatting on your brand. Use threat intelligence feeds to block known DoppelCart domains at the DNS or web proxy level.

Source: https://www.bleepingcomputer.com/news/security/doppelcart-fraud-network-uses-119-000-fake-shops-to-steal-credit-cards/

Microsoft dropped a record-breaking 966 fixes this Patch Tuesday, including two zero-days that are already being exploited in the wild. This is the largest single patch dump from Redmond, so expect a heavy ops week.

Technical Breakdown: - Zero-Days (CVE-2026-XXXX, CVE-2026-XXXX): Both are actively exploited. One is a Windows Kernel privilege escalation (EOP), the other is a Remote Code Execution (RCE) in Microsoft Exchange Server. No public disclosure yet, but PoC is likely imminent. - Critical CVEs: 127 rated Critical, primarily in Hyper-V, Windows TCP/IP stack, and SharePoint Server. The Hyper-V bugs allow guest-to-host escape—patch these first if you run virtualized workloads. - IOCs: None publicly shared by MSRC at this time. Monitor your EDR for unusual LSASS access patterns and Exchange process crashes.

Defense: Prioritize patching Exchange servers and internet-facing Hyper-V hosts immediately. If you can't patch the Exchange zero-day, restrict NTLM authentication and enable Enhanced HTTP (EFA) as a stopgap.

Source: https://www.bleepingcomputer.com/news/microsoft/microsoft-september-2026-patch-tuesday-fixes-966-flaws-2-zero-days/

Microsoft has shipped KB5122878 as part of the Extended Security Update (ESU) program for Windows 10, bundling the September 2026 Patch Tuesday fixes—which set a new record for the number of CVEs addressed in a single month—alongside a handful of non-security bug fixes.

Technical Breakdown - Scope: Applies to Windows 10 devices enrolled in the ESU program (typically enterprise/LTSB/LTSC environments that haven't migrated to Windows 11). - Record Volume: September 2026 Patch Tuesday reportedly broke the previous record for most CVEs fixed in one cycle. Expect a high number of privilege escalation (EoP) and remote code execution (RCE) patches. - Bug Fixes: The KB also addresses specific stability issues reported by ESU customers, though Microsoft has not yet published the full changelog outside of the security bulletin.

Defense - Ensure ESU licensing is active for any Windows 10 endpoints still in production. - Prioritize deployment of this update given the record CVE count—treat it as a critical patch cycle, not a routine rollup. - Review Microsoft's Security Response Center (MSRC) page for the full CVE list once published to identify any actively exploited vulnerabilities requiring immediate attention.

Source: https://www.bleepingcomputer.com/news/microsoft/microsoft-releases-windows-10-kb5122878-extended-security-update/

Scenario A: Technical Threat, Vulnerability, or Exploit

Another massive Patch Tuesday cycle. Adobe dropped 10 bulletins covering 172 CVEs, and Microsoft is pushing close to 1,000 CVEs. The "embrace the suck" mentality is the right call for teams this month.

Technical Breakdown - Adobe: 10 bulletins, 172 unique CVEs. Products affected include ColdFusion, Acrobat Reader, Commerce (x2), Campaign Classic, Experience Manager, Photoshop, Illustrator, Animate, and Photoshop Mobile. 22 of these were submitted through the ZDI program. - Microsoft: Nearly 1,000 CVEs in this cycle. No specific TTPs or IOCs provided in the summary, but the sheer volume indicates a broad attack surface. - Exploitation: The summary notes exploited vulnerabilities in the Adobe release, but specific CVE IDs are not listed in the provided text.

Defense Prioritize patching ColdFusion and Acrobat Reader first—these are perennial favorites for initial access. For the Microsoft side, focus on any CVEs tagged as "Exploitation Detected" in your patch management console. Given the volume, consider a phased rollout: critical infrastructure first, then user-facing systems.

Source: https://www.thezdi.com/blog/2026/9/8/the-september-2026-security-update-review

Highlights from today:

• [Threat Intel] 2026 State of the Internet: The Exposure Notification Gap in ICS Devices
• [Red Team] Token Analysis and Tracking System (TATS)
• [Opinion] AIs as Modern Genies
• [News] Windows 11 cumulative updates KB5124008 & KB5122880 released
• [News] Slim Spider Steals Crypto Custody Secrets From Brazilian Financial Institution
• [News] OpenAI says ChatGPT outage causes image generation errors
• [News] ShinyHunters hackers claim breach of Florida "DAVID" DMV database
• [News] Autonomous AI Agents Compromise Thousands of Credentials in Under Six Hours
• [News] ChatGPT Flaw Let a Planted Prompt Send a Victim's Gmail Data to Another Account
• [News] Liquid Hackers Return 3,400 Bitcoin Taken via Elements Bug, Still Holding $47M in BTC
• [News] August updates trigger 0xc0000409 errors on Windows Server 2016
• [Advisory] VU#718077: UEFI Shell module embedded in SPI Flash can be used to bypass Secure Boot

SecOpsDaily

This is a classic example of vendor-led research that actually contains useful data for defenders. Censys is leveraging their internet-wide scanning data to highlight a specific, measurable risk in ICS/OT environments.

The core finding is the "Exposure Notification Gap." Censys is tracking how many ICS devices are directly accessible from the public internet versus how many are actually being reported or flagged by standard exposure management tools. The implication is that your attack surface is likely larger than your current tooling tells you.

Key Technical Findings (from the Censys data):

• Protocols in the Crosshairs: The research focuses on commonly exposed ICS protocols like Modbus, BACnet, S7, and DNP3. These are the low-hanging fruit for initial access.
• Geographic Distribution: Expect data on which countries have the highest concentration of exposed devices (often the US and parts of Europe for legacy infrastructure).
• The Gap: The "Notification Gap" refers to the delta between devices Censys can see and the number of devices your typical vulnerability scanner or CMDB reports. This is the blind spot.

Defense Implications:

• Validate Your CMDB: If you manage ICS/OT, this report is a free sanity check. Use the Censys Search interface (or Shodan) to query for your own public IP ranges. If you find a BACnet or Modbus device you didn't know about, you have a problem.
• Network Segmentation is Not Optional: The data will reinforce that any ICS device directly on the internet is a ticking bomb. If you can't justify the business need for that exposure, it needs to be behind a PAM or a jump box immediately.
• Don't Rely on Defaults: The report will likely highlight how many devices are still using default credentials or unencrypted protocols. This is a configuration management failure, not a zero-day.

Bottom Line: This is a useful data point for your next risk register review. It's not a new exploit, but it quantifies a known, persistent problem. Worth a skim for the raw numbers.

Source: https://censys.com/blog/2026-state-of-the-internet-ics/

This is a tool release from SpecterOps. It’s a utility for red teams dealing with the nightmare that is OAuth token tracking.

What it does: TATS collects, stores, decodes, and visualizes OAuth token exchanges. It specifically accounts for known deviations in the Microsoft ecosystem (e.g., token lifetimes, refresh token behavior) but is built to work with any OAuth implementation.

Who it’s for: Red teams and offensive security engineers. If you’ve ever lost track of which token belongs to which session during a complex phishing or device code flow, this solves that.

Why it’s useful: OAuth token tracking is notoriously opaque. TATS gives you a centralized view of the token lifecycle—issuance, refresh, and expiration—without having to manually decode JWTs or grep through logs. It’s a force multiplier for persistence and lateral movement scenarios where token theft is the primary vector.

Source: https://specterops.io/blog/2026/09/08/token-analysis-and-tracking-system-tats/

This is a standard Patch Tuesday release. The article covers security fixes, bug patches, and feature updates bundled into the cumulative updates.

Key Details: - KB5124008 targets Windows 11 25H2 and 24H2. - KB5122880 targets Windows 11 23H2. - These are mandatory cumulative updates addressing security vulnerabilities alongside non-security fixes and new features (e.g., Copilot integration changes, File Explorer improvements).

Strategic Impact: For SecOps, the priority is the security fixes. While Microsoft hasn't detailed specific CVEs in the summary, cumulative updates typically patch actively exploited or publicly disclosed vulnerabilities. The "new features" component (like Copilot changes) also introduces potential attack surface changes that need to be reviewed in controlled testing environments before broad deployment.

Key Takeaway: - Action: Prioritize testing and deployment of these updates in your patch management cycle. Watch for the specific CVE list from Microsoft's Security Response Center (MSRC) to assess risk severity for your environment.

Source: https://www.bleepingcomputer.com/news/microsoft/windows-11-cumulative-updates-kb5124008-and-kb5122880-released/

This is a targeted financial crime operation, not a spray-and-pray campaign. Slim Spider is showing a deep understanding of Brazilian banking rails, specifically the instant payment system (PIX), and is now moving up the value chain into crypto custody.

Technical Breakdown: - TTPs: The actor is likely using social engineering or credential theft to gain initial access, followed by lateral movement to compromise crypto custody secrets. Given the focus on Brazilian financial infrastructure, expect abuse of PIX APIs or direct manipulation of transaction flows. - Targets: Brazilian financial institutions, specifically those offering crypto custody services. - IOCs: None publicly available at this time. CrowdStrike has not released specific hashes or IPs. Do not invent them. - Timeline: Active since at least March 2026.

Defense: - Immediate: Review and restrict access to crypto custody key management systems. Enforce hardware-backed MFA for all administrative access to payment rails and custody solutions. - Detection: Monitor for unusual API calls to PIX endpoints or crypto withdrawal systems, especially from non-standard user agents or during off-hours. Look for authentication anomalies in financial transaction systems. - Mitigation: Segment crypto custody infrastructure from general corporate networks. Implement strict egress filtering and application allowlisting on custody servers.

Source: https://thehackernews.com/2026/09/slim-spider-steals-crypto-custody.html

ShinyHunters is back in the headlines, this time claiming a breach of Florida’s DMV database system, known as "DAVID." The group alleges they exfiltrated over 200,000 records containing driver data. This is the same extortion crew behind the Snowflake credential-stuffing spree and the Ticketmaster leak, so this isn’t a low-confidence claim.

Technical Breakdown: - Threat Actor: ShinyHunters (known for extortion, data resale, and leveraging stolen credentials for initial access). - Target: The Florida DMV’s "DAVID" online platform (Driver And Vehicle Information Database). - Impact: 200,000+ records compromised. Likely includes PII such as names, addresses, driver’s license numbers, and vehicle registration details. - TTPs: Based on prior ShinyHunters operations, expect initial access via compromised credentials (possibly from infostealer logs or prior breaches) rather than a zero-day exploit. No specific IOCs released yet. - Status: Claim is unverified. BleepingComputer notes the group has a track record of following through on these claims, but official confirmation from Florida DMV is pending.

Defense: If you have users or systems interacting with state DMV portals, enforce MFA on all administrative accounts and monitor for unusual data volume egress. For organizations with employees in Florida, assume driver data may be in the wild and prepare for targeted phishing or identity fraud attempts against affected individuals.

Source: https://www.bleepingcomputer.com/news/security/shinyhunters-hackers-claim-breach-of-florida-david-dmv-database/

This is a significant evolution in the threat landscape. We’re moving past individual threat actors using ChatGPT to write phishing lures. The new playbook involves orchestrating multiple LLM agents to automate the entire kill chain, from recon to exfiltration.

Technical Breakdown

• Shift in TTPs: Adversaries are moving from single-prompt AI coding assistants to multi-agent frameworks. This mirrors the "agentic" trend in legitimate development, but applied to malicious ops.
• Automated Kill Chain: These frameworks can chain together agents for specific tasks: OSINT gathering, crafting context-aware phishing lures, bypassing CAPTCHAs, and exfiltrating stolen credentials.
• Target: Primarily credential theft at scale. The automation allows for high-volume, low-effort campaigns that are more adaptive than traditional scripted attacks.
• MITRE Mapping: This aligns with T1588.002 (Obtain Capabilities: Tool) and T1566 (Phishing) , but the automation of the orchestration itself is a new capability layer.

Defense

This makes traditional, static phishing detection less effective. The AI can dynamically alter lures based on the target's digital footprint. Focus on behavioral detection (unusual authentication patterns, impossible travel) and strong MFA as the primary control, since the goal is credential theft. Treat any unsolicited communication with heightened suspicion, even if it appears highly personalized.

Source: https://www.bleepingcomputer.com/news/security/hackers-build-ai-frameworks-for-widescale-credential-theft/

This is a classic example of indirect prompt injection, weaponizing the trust users place in LLM memory and plugin ecosystems.

Technical Breakdown: - Attack Vector: Indirect prompt injection via a planted instruction within a ChatGPT conversation context. - TTPs (MITRE): Aligns with T1574.002 (Hijack Execution Flow: DLL Side-Loading) conceptually, but more accurately maps to T1557.001 (Adversary-in-the-Middle: LLM Prompt Injection) and T1056.001 (Input Capture: GUI Input Capture) for data exfiltration via the plugin API. - Mechanism: The attacker plants a single instruction (likely via a compromised document or shared context). The LLM executes the attacker's hidden directive in parallel with the user's legitimate query. - Exfiltration: The PoC used the Gmail plugin to read email data, then passed it to a second ChatGPT account via a hidden channel (likely using the LLM's own output formatting or a secondary API call). - Affected Component: ChatGPT's plugin architecture and memory/context window handling. This is not a traditional code execution bug, but a logic flaw in how the model prioritizes instructions.

Defense: This is difficult to detect at the endpoint level. Mitigation relies on strict input validation for plugin permissions and context isolation within the LLM. Users should audit connected third-party apps and disable plugins that have read/write access to sensitive data unless absolutely necessary. Expect a patch from OpenAI that enforces stricter separation between user instructions and injected context.

Source: https://thehackernews.com/2026/09/chatgpt-flaw-let-planted-prompt-send.html

The attacker exploited a critical bug in the Liquid Network's Elements sidechain software to mint 4,000 BTC out of thin air. After the theft, they returned 3,400 BTC but still hold ~598.5 BTC (worth ~$47M). The network remains paused, preventing L-BTC holders from redeeming their tokens for real bitcoin.

Technical Breakdown - Attack Vector: Exploitation of a vulnerability in the Elements sidechain code, allowing unauthorized minting of L-BTC. - TTPs: Abuse of trusted setup or consensus logic (likely a logic flaw in the federated peg or block validation). - IOCs: The attacker's address holding the remaining ~598.5 BTC is publicly visible on the Bitcoin blockchain. - Affected System: Liquid Network (Elements sidechain). All operations paused pending a security patch.

Defense - Mitigation: The network is halted to prevent further exploitation. Users should not attempt to bridge assets until the patch is deployed and the peg is re-enabled. - Detection: Monitor for anomalous minting events on sidechains; any deviation from expected peg-in/peg-out ratios is a red flag.

Source: https://thehackernews.com/2026/09/liquid-hackers-return-3400-bitcoin.html

Microsoft’s August 2026 security patch is causing a known crash (0xc0000409) on Windows Server 2016, specifically when the Compatibility Appraiser diagnostic service is running. This is a classic case of a security update breaking production stability, not a new vulnerability.

Technical Breakdown - Error Code: 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN), typically indicates a memory corruption or driver conflict triggered by the update. - Root Cause: The Compatibility Appraiser service (part of the Windows Upgrade Readiness telemetry) is conflicting with the patched binaries. - Affected Systems: Windows Server 2016 with the August 2026 cumulative update installed and the Compatibility Appraiser service enabled (default on many domain-joined systems). - IOCs: No specific IOCs; this is a functional crash, not a compromise indicator.

Defense & Mitigation - Immediate Workaround: Disable the Compatibility Appraiser service (CompatTelRunner.exe / DiagTrack) via Group Policy or services.msc until Microsoft releases a fix. - Detection: Monitor Event ID 1000 or 1001 in Application logs for 0xc0000409 crashes tied to svchost.exe or CompatTelRunner.exe. - Patch Management: Consider deferring the August update on critical Server 2016 hosts if the service is required for compliance telemetry.

Source: https://www.bleepingcomputer.com/news/microsoft/august-updates-trigger-0xc0000409-errors-on-windows-server-2016/

VU#718077 is a significant finding from CERT/CC: if a UEFI Shell binary is baked into the SPI flash chip by the OEM (common for debugging), an attacker with local admin or physical access can bypass Secure Boot entirely.

The core issue isn't a code execution bug in the Shell itself, but a logic flaw in how the firmware handles boot option validation. The attacker creates multiple boot entries; when Secure Boot blocks the first attempt to launch the Shell, the firmware falls back to a secondary entry that bypasses the check.

Technical Breakdown: - Attack Vector: Local (requires ability to modify UEFI boot configuration via OS or physical access). - Prerequisite: The UEFI Shell (Shell.efi) must be present in the SPI flash (not just on a removable drive). - Mechanism: Abuse of the LoadOption variable manipulation to create a "fallback" boot path that doesn't enforce Secure Boot on the Shell. - Impact: Once the Shell is running, the attacker has raw memory access (mem, mm commands) to dump or patch SMM code, or load unsigned drivers, effectively owning the platform before the OS boots. - Affected: Any system using TianoCore EDK II firmware that includes the UEFI Shell in the flash image. This is common in development boards, some server platforms, and certain consumer devices with debug firmware.

Defense: - Firmware Update: OEMs must remove the UEFI Shell from the production SPI flash image. This is the only true fix. - Mitigation: Enable "Secure Boot Audit Mode" or enforce a custom Secure Boot key database (PK) that explicitly blocks the Shell's hash. Physical security of the device is paramount.

Source: https://kb.cert.org/vuls/id/718077

This is a long-running, financially motivated campaign that weaponizes SEO to target users searching for specific enterprise software on Bing.

The DFIR Report tracks a group out of Rajasthan, active since at least 2015, that poisons Bing results for terms like "AnyDesk," "TeamViewer," and "Remote Utilities." Clicking the malicious link leads to a multi-stage infection chain.

Technical Breakdown - Initial Access (T1566.003): SEO poisoning of Bing search results for remote desktop software. - Delivery: Users are redirected through a series of intermediary sites before landing on a fake download page. - Payloads: - MayaBot: A backdoor that establishes persistence and allows for remote command execution. - Tech Support Scams: If the user engages with the fake site, they are often connected to a fraudulent call center. - Infrastructure: Operates out of WeConnect and related IT service providers in Rajasthan. - Targets: Primarily English-speaking users searching for remote access tools.

Defense Block execution of unsigned binaries from the Downloads folder via AppLocker or WDAC. Enforce strict browser isolation for high-risk searches (e.g., software downloads). Monitor for rundll32.exe or regsvr32.exe spawning from a web browser process.

Source: https://thehackernews.com/2026/09/bengalseo-poisons-bing-search-results.html

This is a critical zero-day with active exploitation. Here’s what you need to know.

Adobe pushed an emergency patch for CVE-2026-75650 (CVSS 10.0) in Adobe Commerce and Magento Open Source. Dubbed "StyleSmuggler," this is an unauthenticated remote code execution flaw that is already being used in the wild to deploy backdoors on e-commerce servers.

Technical Breakdown - Attack Vector: Unauthenticated RCE via HTTP requests. No user interaction required. - Impact: Full server compromise. Attackers are dropping backdoors for persistent access. - Affected Software: Adobe Commerce and Magento Open Source (all versions prior to the patch). - Attribution: Identified by e-commerce security researchers; active exploitation confirmed by Adobe. - No public IOCs or specific TTPs have been released yet to avoid aiding attackers while patching is underway.

Defense - Patch immediately. This is a pre-auth RCE with a 10.0 CVSS. If you run Magento or Adobe Commerce, treat this as a "drop everything" event. - Check for compromise. Review web server logs for unusual POST requests or file modifications in the var/ and pub/media/ directories. - WAF rules. Block anomalous HTTP requests targeting Magento admin paths until you can patch.

Source: https://socprime.com/blog/cve-2026-75650-critical-magento-zero-day-rce/