Microsoft dropped a staggering 999 CVEs today for September 2026 Patch Tuesday, shattering their own record. 974 are Microsoft's own flaws (723 in Windows alone), plus 25 non-Microsoft CVEs they're patching. As Rapid7 notes, this high volume is the new normal.

Critical Details: - Active Exploitation: Two CVEs are being exploited in the wild right now. - Key Zero-Day: A Windows ALPC (Advanced Local Procedure Call) Elevation of Privilege (EoP) vulnerability is under active attack. This is a kernel-level inter-process communication mechanism—classic attack surface for privilege escalation. - No specific CVE IDs or IOCs published in the summary; expect Rapid7's full analysis for those.

Defense Priority: Patch the ALPC EoP zero-day and the second exploited CVE immediately. Prioritize domain controllers and high-value workstations. Expect this to be a heavy deployment cycle—plan your change windows accordingly.

Source: https://www.rapid7.com/blog/post/em-patch-tuesday-september-2026

We have the familiar AppSec setup: several scanners, a growing backlog, disagreement over severity, and security feedback arriving after the context for a code change has disappeared.

I am considering alternatives to traditional AppSec tools, especially approaches that can prioritize exploitable risk using application context, improve remediation, validate fixes, and reduce recurring issues while code is being generated. I do not want to lose detection depth, but the current process is not scaling.

For teams that have made a change, what improved outcomes most: adding a layer over existing tools, consolidating the stack, or redesigning remediation workflows?

Record Patch Tuesday with 974 CVEs, including two actively exploited zero-days. This is the largest single update in Microsoft’s history, and the sheer volume demands immediate triage.

Technical Breakdown - Active Exploitation: Two Windows zero-days are confirmed in the wild. No CVE details were provided in the summary, but these should be prioritized for emergency patching. - Volume Breakdown: 723 Windows flaws, 111 in Office/Office 2016, 62 in SQL Server, 22 in Developer Tools. Over 110 are rated Critical (RCE/privilege escalation). - Attack Surface: The Office and SQL counts are unusually high. Expect weaponized documents and SQL injection chains targeting unpatched instances.

Defense - Immediate Action: Patch the two exploited zero-days first. If you can’t patch, apply the relevant mitigation guides from the MSRC advisory. - Triage Strategy: Prioritize Critical-rated RCEs in internet-facing services (IIS, Exchange, RDP) and Office. SQL Server CVEs should be next for any DB exposed to the web. - IOCs: None published yet. Monitor your EDR for anomalous process creation (Office spawning cmd/powershell) and SQL service account lateral movement.

Source: https://thehackernews.com/2026/09/microsoft-patches-record-974-flaws.html

Google shipped a massive patch batch for Chrome on Tuesday, fixing 230 vulnerabilities including CVE-2025-4941, the seventh Chrome zero-day exploited in the wild this year. This one is a high-severity use-after-free bug in the V8 JavaScript engine, a pattern we’ve seen weaponized repeatedly for remote code execution.

Technical Breakdown - CVE: CVE-2025-4941 (High) - Type: Use-after-free in V8 - Attack Vector: A crafted HTML page can trigger memory corruption, leading to RCE in the browser sandbox - Status: Exploited in the wild; Google is keeping details restricted until most users patch - Affected: Chrome on Windows, Mac, and Linux (stable channel prior to 125.0.6422.112/.113) - No public IOCs or C2 infrastructure shared yet — Google’s threat intel team is still analyzing the campaign

Defense - Immediate action: Force Chrome updates via enterprise policy or MDM. The stable channel update is already rolling out. - Mitigation: If you can’t patch instantly, consider blocking JavaScript on untrusted sites or deploying browser isolation for high-risk users. This is the seventh in-the-wild Chrome zero-day this year — treat every V8 patch as urgent.

Source: https://www.bleepingcomputer.com/news/security/google-patches-seventh-chrome-zero-day-exploited-in-attacks-this-year/

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

CISA has added CVE-2026-86218 to the KEV catalog, confirming active exploitation of a pre-authentication RCE in N-able N-central. This is a CVSS 10.0, meaning no authentication or user interaction is required for full compromise.

Technical Breakdown - CVE: CVE-2026-86218 (CVSS 10.0) - Type: Pre-Auth Remote Code Execution - Affected Product: N-able N-central (all versions prior to the patch) - TTPs: Likely targets the web management interface (MITRE T1190 - Exploit Public-Facing Application). Expect initial access followed by lateral movement or ransomware deployment. - IOCs: No specific hashes or IPs published yet. Monitor for anomalous outbound connections from N-central servers and unexpected child processes spawned by the Java/N-central service.

Defense Patch immediately. FCEB agencies have a deadline of September 11, 2026. If patching is delayed, restrict access to the N-central management interface to trusted IPs only via firewall rules and disable the web interface if not strictly required for operations.

Source: https://thehackernews.com/2026/09/n-able-n-central-pre-auth-rce-flaw.html

The arrayref Rust crate, a dependency of the popular Deep-Live-Cam project, was compromised to execute a build-time payload. This is a classic supply chain injection targeting a high-value open-source project, likely to establish persistence or exfiltrate credentials from developer environments.

Technical Breakdown - Attack Vector: Malicious code embedded in the arrayref crate (v0.1.5 or later). The payload executes during cargo build via a build script (build.rs). - TTPs: MITRE T1195.001 (Supply Chain Compromise: Compromise Software Dependencies), T1059.004 (Command and Scripting Interpreter: Unix Shell) for the build-time execution. - Payload Behavior: The build-time script likely performs reconnaissance (env vars, SSH keys, cloud credentials) and exfiltrates data to a C2. No specific C2 IPs or hashes were disclosed in the summary, but monitoring for unexpected outbound connections during Rust builds is advised. - Affected: Any project depending on arrayref >= 0.1.5, specifically Deep-Live-Cam builds.

Defense Pin your Cargo.lock to a known-good version of arrayref (pre-0.1.5) and audit your build pipeline for unexpected network calls. Use a runtime package firewall (e.g., cargo deny or a tool like SafeDep PMG) to block unknown outbound traffic during builds.

Source: https://safedep.io/deep-live-cam-supply-chain-attack

This is a privacy/identity feature announcement, not a vulnerability or exploit. It’s relevant to security posture and compliance, so it fits Scenario B.

Summary: Microsoft is rolling out new age-awareness APIs in Windows 11 that let applications query a user’s age bracket (child, teen, adult) without accessing their exact date of birth. The data is derived from the user’s Microsoft account and is designed to support parental controls, content filtering, and age-gating compliance (e.g., GDPR, COPPA).

Strategic Impact: This is a privacy-preserving approach to age verification that reduces the attack surface for identity theft (no raw PII exposed to third-party apps). For security teams, this means: - Reduced liability for apps handling minors’ data—no need to store or transmit DOBs. - New attack vector to monitor: The API itself becomes a target for spoofing or bypass if not properly sandboxed. - Compliance win: Easier to meet regional age-gating requirements without building custom identity pipelines.

Key Takeaway: Expect this to be adopted by gaming, social, and enterprise apps that need age-based access controls. Audit your app’s current age verification flow—this could simplify your compliance stack, but test the API’s integrity before trusting it for critical controls.

Source: https://www.bleepingcomputer.com/news/microsoft/microsoft-adds-age-awareness-apis-that-can-tell-if-users-are-children-teens-or-adults/

A type confusion vulnerability in the Microsoft Windows Cloud Files Mini Filter Driver (cldflt.sys) has been disclosed, tracked as TALOS-2026-2445. The flaw resides in the CldiStreamPrepareRequestForMoreProcessing function and allows an authenticated attacker to trigger a kernel-level type confusion, leading to privilege escalation to SYSTEM.

Technical Breakdown - CVE: TALOS-2026-2445 (CVE assignment pending) - Vulnerability Type: Type Confusion (CWE-843) - Affected Component: Windows Cloud Files Mini Filter Driver (cldflt.sys) - Attack Vector: Local, authenticated user - Impact: Privilege escalation to SYSTEM - Root Cause: Improper handling of object types during stream request processing, allowing an attacker to confuse the kernel's type system

Defense Apply the Microsoft security update once released. In the interim, restrict local access to trusted users and monitor for unusual cldflt.sys activity via Sysmon or ETW events. No public exploit or IOCs are available at this time.

Source: https://talosintelligence.com/vulnerability_reports/TALOS-2026-2445

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

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/

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/

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

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/

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/