Coverage: Last 24 hours
Today’s Highlights
A surge of critical vulnerabilities hits major platforms, with defenders facing live exploitation and escalating attacker sophistication across endpoint, cloud, and IoT. Patch discipline, rapid detection, and targeted access reviews are essential to avoid disruptions and prevent deeper compromise. Key themes include widespread Microsoft and Cisco vulnerabilities, attackers leveraging AI and decentralized tools, advanced social engineering, supply chain risks, and new DDoS and ransomware strategies.
Table of Contents
- Microsoft Plugs Nearly 400 Security Holes
- Kimwolf v7 Android Botnet Makes HTTP/2 DDoS Traffic Look Like Legitimate Browsing
- Zoom Annotation Flaws Could Let a Meeting Participant Hijack Another Attendee’s Client
- Sandworm-Linked UAC-0145 Uses Fake Job Interviews to Push VPN That Can Run Commands
- DeadLock Ransomware Uses Polygon Smart Contracts to Make Extortion Infra Harder to Disrupt
- A Malicious SIM Card Can Run Attacker Code Inside the Modems Behind Cellular IoT Devices
- Mozilla Revokes Firefox and Thunderbird Linux Signing Key After Key Lands in Private Repo
- Researchers Built a Fake Crypto Startup and Hired Three Suspected North Korean IT Workers
- Microsoft Patches 398 Flaws Including a Windows Driver Zero-Day Under Active Attack
- Researchers Disclose AI-Assisted SharePoint Exploit Chain Reaching Unauthenticated RCE
- OpenAI Launches GPT-5.6-Cyber with Reduced Safeguards for Exploit Development
- Cisco Patches Firewall Zero-Day Exploited for DoS Attacks
Top Stories
Microsoft Plugs Nearly 400 Security Holes
Source: Krebs on Security | Risk: Critical | Impacted: Windows server operators, Azure tenants, Workstations running Microsoft endpoint software, IT admin teams relying on delayed patch approval
Summary: Microsoft today released updates to remedy at least 398 security vulnerabilities in its Windows operating systems and supported software, including one weakness that is already being actively exploited and two others that were publicly detailed prior to today.
Why it matters: A backlog of unresolved vulnerabilities across the Microsoft ecosystem increases the window for attackers to exploit unpatched systems, particularly when some issues are already under active attack or have public exploit code.
Practitioner Perspective
Organizations relying on Windows infrastructure face heightened risk when patch cycles are delayed, especially given confirmed in-the-wild exploitation of at least one vulnerability and advance disclosures on others. The sheer volume of patches this month means prioritization is critical: focus on those under active exploitation and those with public proof of concept, but do not ignore less visible components in enterprise environments. Attacks often follow these releases, targeting systems that lag behind in patch deployment. Expect upticks in exploit attempts for weeks post-release, especially in externally exposed endpoints. Make sure patch validation and exception handling workflows are robust, automation is not a substitute for oversight.
Recommended Actions
- Immediately review and deploy August 2026 Microsoft security updates, focusing first on issues with confirmed exploitation and public details
- Cross-check all Windows endpoints for patch compliance, especially those running mission-critical services
Emerging Signals
Kimwolf v7 Android Botnet Makes HTTP/2 DDoS Traffic Look Like Legitimate Browsing
Source: The Hacker News | Risk: High | Impacted: Organizations with publicly accessible web applications, High-traffic API endpoints, ISPs handling customer DDoS mitigation, Deployers of vulnerable IoT devices
Summary: Cybersecurity researchers have discovered a new version of the Kimwolf/AISURU Android and Internet of Things (IoT) botnet that comes with significant improvements to improve its operational resilience and conduct distributed denial-of-service (DDoS) attacks. The new version, tracked as Kimwolf v7, was discovered by Palo Alto Networks Unit 42 in February 2026. “Kimwolf v7 adds an HTTP/2-based”.
Why it matters: Attackers leveraging Kimwolf v7 undermine traditional DDoS detection by mimicking valid user traffic over HTTP/2, making disruption of web-facing infrastructure more difficult to quickly discern and stop.
Practitioner Perspective
Android and IoT botnets are evolving to evade longstanding rule-based defenses, using new protocols and behavioral tweaks to appear legitimate in volumetric DDoS attacks. This blurring between attack and normal web activity puts serious strain on response teams, especially for organizations with limited visibility into HTTP/2 traffic profiles. Containment now hinges on behavioral analytics and rapid collaboration with upstream providers. Proactive defense requires both tuning of filters and simulated red team DDoS exercises using similar tactics. Defenders need to anticipate that these evasive methods will proliferate in for-hire DDoS crews.
Recommended Actions
- Tune web application firewalls and DDoS mitigation services for anomalous HTTP/2 request bursts and malformed patterns identified in Kimwolf v7 reports
- Coordinate with ISP or cloud providers to improve detection of botnet sources using Android/IOT signatures
Zoom Annotation Flaws Could Let a Meeting Participant Hijack Another Attendee’s Client
Source: The Hacker News | Risk: High | Impacted: Organizations conducting frequent external Zoom meetings, Educational institutions, Remote workforces using BYOD for video calls
Summary: Anyone sharing their screen on a Zoom call could have taken over the computers of everyone watching, and anyone watching could have taken over the presenter’s. The flaw sat in the annotation tool, the feature that lets participants draw and type on a shared screen, and it asked nothing of the victim beyond being in the meeting. No click, no.
Why it matters: The annotation tool vulnerability in Zoom allows any meeting participant to potentially execute code on another participant’s or the presenter’s system, which subverts trust boundaries in collaborative environments.
Practitioner Perspective
Corporate Zoom deployments are especially at risk in environments where external or lightly vetted users regularly join meetings. This flaw, requiring no victim interaction beyond presence, bypasses common user awareness protections and could be abused for rapid internal compromise or to pivot through corporate laptops. Restricting use of annotation features is now a necessary mitigation until all clients are patched. Security teams should extend focus beyond traditional endpoint and network defenses: policy control over collaboration tooling is now critical for lateral movement risk reduction.
Recommended Actions
- Disable or restrict Zoom annotation features via admin settings on managed clients pending patch application
- Ensure latest Zoom client updates are installed across all endpoints
Sandworm-Linked UAC-0145 Uses Fake Job Interviews to Push VPN That Can Run Commands
Source: The Hacker News | Risk: High | Impacted: IT departments, DevOps staff, Organizations with operations in Ukraine or high geopolitical exposure
Summary: The Computer Emergency Response Team of Ukraine (CERT-UA) has disclosed details of a new social engineering campaign orchestrated by Russian nation-state threat actors targeting IT workers in the country by masquerading as recruiters to trick them into installing malware. CERT-UA pinned the activity on a threat cluster it tracks as UAC-0145, which is a subgroup within Sandworm (aka APT44,).
Why it matters: Sophisticated social engineering campaigns targeting IT professionals can bypass legacy perimeter controls, planting malware with privileged access deep in core infrastructure.
Practitioner Perspective
Russia-linked APT actors are escalating use of fake recruitment schemes aimed at technical staff, increasing risk to organizations whose IT teams receive unsolicited job offers or recruiter inquiries. These operations abuse IT staff trust and technical proficiency, often resulting in the installation of payloads with VPN or RMM capabilities. Once an attacker is inside via an IT user’s machine, they are well-positioned for network-wide lateral movement or data theft. Security teams must treat workforce phishing defense and user education as a critical control for insider-like threat models.
Recommended Actions
- Implement targeted phishing simulation training for IT and developer staff focusing on fake recruiter scenarios
- Monitor for installation of unauthorized VPN or remote access tools on admin workstations
DeadLock Ransomware Uses Polygon Smart Contracts to Make Extortion Infra Harder to Disrupt
Source: The Hacker News | Risk: High | Impacted: Victims of targeted ransomware attacks, Incident responders handling DeadLock intrusions, Organizations with sensitive or regulated data at risk of leaks
Summary: The ransomware group known as DeadLock has been observed using decentralized infrastructure to facilitate victim communications and data leak operations in a bid to improve operational resilience. “Its recovery ecosystem combines the Session messaging network with blockchain-backed services that store and deliver resources used throughout the extortion process,” the Microsoft Threat.
Why it matters: DeadLock ransomware’s use of smart contracts and decentralized messaging undermines traditional intervention points, making it harder for response teams to disrupt negotiations or block leak site infrastructure.
Practitioner Perspective
Ransomware crews are moving infrastructure to decentralized and blockchain-backed networks, limiting defender leverage over payment and extortion workflows. Enterprises should assume that even if a hosting or DNS provider cooperates, new leak sites or communication channels will appear rapidly on distributed platforms. Incident teams must update playbooks to account for irreversible smart contract payments and ephemeral data posts. The shift also increases the risk that ransom payment tracking will be more opaque to threat intelligence. Disruption now demands faster, more coordinated legal and technical takedowns.
Recommended Actions
- Monitor for known DeadLock ransomware TTPs and be ready to engage with decentralized domains or session-based communications
- Prepare executive/legal response for Polygon smart contract-based extortion attempts
A Malicious SIM Card Can Run Attacker Code Inside the Modems Behind Cellular IoT Devices
Source: The Hacker News | Risk: High | Impacted: Operators of industrial IoT fleets, Automotive telematics vendors, Critical infrastructure providers
Summary: A malicious SIM card can order the device it sits in to run commands of the attacker’s choosing. On the cellular modules built into electric-vehicle chargers, industrial routers, and car telematics units, that is enough to take the whole device over. Researchers at the University of Birmingham and the security firm Fuzzware tested 26 phones and cellular modules for the.
Why it matters: Malicious or compromised SIM cards in cellular-connected IoT devices can be a low-visibility entry point for attackers to commandeer industrial or vehicular infrastructure, threatening both data integrity and operational safety.
Practitioner Perspective
Many organizations deploying cellular-connected devices, including EV chargers, industrial routers, and telematics, overlook the risk of code execution via SIM card channels. Threat actors exploiting this vector can bypass network perimeter controls and may gain persistent access or control over fleets of devices. Effective governance of SIM provisioning and inventory is now a critical asset management concern, particularly as SIM attacks are difficult to detect by traditional network or endpoint means. Rigorous supply chain validation and vendor diligence are non-negotiable for organizations with critical field-deployed cellular systems.
Recommended Actions
- Inventory all SIM cards deployed across cellular-connected IoT and OT devices
- Validate SIM provenance and carrier controls in procurement workflows
Mozilla Revokes Firefox and Thunderbird Linux Signing Key After Key Lands in Private Repo
Source: The Hacker News | Risk: High | Impacted: Linux desktop and server admins, Enterprise Linux distributions, Open-source software packagers
Summary: Mozilla has scrapped the cryptographic key behind Firefox and Thunderbird downloads for Linux after an unencrypted copy of it was committed by mistake to one of the company’s own private code repositories. That key is how a user, or a Linux distribution packaging the browser, confirms a downloaded Firefox tarball came from Mozilla and was not tampered with. That decision.
Why it matters: Exposure of Mozilla’s Linux signing key creates a window where tampered binaries could have been distributed to users, undermining foundational trust in update and deployment chains.
Practitioner Perspective
Distributors and users of Firefox and Thunderbird for Linux need to scrutinize any binaries obtained during the period the exposed key may have been misused. Even accidental key exposure in a private repo enables sophisticated attackers to forge code and package updates, potentially facilitating wide-scale supply chain attacks. Downstream packagers must act quickly to revoke and replace affected builds. Auditable builds and artifact chain-of-custody become essential controls for all open-source consumers as risks here ripple out to entire ecosystems.
Recommended Actions
- Review hash integrity and provenance of Firefox and Thunderbird installers acquired during the affected signing key period
- Update to Mozilla-approved versions re-signed with the new key for both browsers
Researchers Built a Fake Crypto Startup and Hired Three Suspected North Korean IT Workers
Source: The Hacker News | Risk: High | Impacted: Crypto startups, Fintech hiring teams, Remote DevOps and developer operations
Summary: Security researchers invented a cryptocurrency startup, advertised developer jobs, and hired three people they believe were North Korean operatives. Every virtual machine the company issued was recording. The onboarding paperwork is the part hiring teams can use. The first hire claimed to live in Pasadena, Texas, then sent a California driver’s license and a New York bank account. The.
Why it matters: North Korean IT operatives continue to evade direct attribution, securing contracts with Western companies to obtain sensitive infrastructure access, leak intellectual property, or launder funds.
Practitioner Perspective
The use of elaborate social engineering and false-flag identities enables sanctioned actors to embed themselves as trusted insiders in fintech and crypto-adjacent firms. Background checks and onboarding controls are failing to detect synthetic identities and fake provenance, with attackers adept at leveraging real national documentation. Security teams should treat all remote developer hires, especially those handling sensitive software supply chain roles, with heightened suspicion and regular audit. Automated activity recording and staged onboarding are proving useful for exposure but are no substitute for strong verification.
Recommended Actions
- Implement enhanced verification of candidate identities, especially for remote developer positions in sensitive environments
- Monitor onboarding and offboarding workflows for signs of synthetic identity or document forgery
Exploits & CVEs
Microsoft Patches 398 Flaws Including a Windows Driver Zero-Day Under Active Attack
Source: The Hacker News | Risk: Critical | Impacted: Windows enterprise endpoints, Domain-joined workstations, RDS farms, Organizations with kiosk/public devices
Summary: Microsoft released its monthly security updates on Tuesday, and one of the flaws it closed is already being used in attacks. The bug sits in a core Windows kernel driver that handles network socket operations. An attacker with code already running on a machine can use it to escalate to SYSTEM. That patch goes out first. The flaw is tracked
Why it matters: A privilege escalation flaw in a core Windows kernel driver enables local attackers to attain SYSTEM control, representing a direct path from basic compromise to total host takeover.
Practitioner Perspective
Any scenario granting attackers local code execution, phishing, malware, or insider threat, can now lead directly to system-level access via this kernel driver vulnerability if unpatched. This broadens the blast radius for commodity and targeted attacks alike. Windows kernel flaws are especially attractive for lateral movement in hybrid enterprise networks. Environments with user-facing or kiosk systems are especially vulnerable to local escalation vectors. Defensive attention must pivot immediately to patch status and retroactive detection for suspicious privilege elevation correlated with network socket operations.
Recommended Actions
- Deploy the August 2026 patch for the affected Windows kernel network driver on all endpoints
- Hunt for unusual SYSTEM-level process creation following user logins via EDR solutions
Researchers Disclose AI-Assisted SharePoint Exploit Chain Reaching Unauthenticated RCE
Source: The Hacker News | Risk: Critical | Impacted: SharePoint Server admins, Hybrid on-prem/cloud Microsoft shops, Firms with client-facing SharePoint portals
Summary: Security researchers found a way to enter Microsoft SharePoint servers as any user, including an administrator, with no valid account. A significant part of the work that found it was done through an AI agent. The flaw, tracked as CVE-2026-55040 (CVSS 9.1), affects SharePoint Server Subscription Edition, SharePoint Server 2019, and SharePoint Server 2016. Microsoft’s
Why it matters: Unpatched SharePoint servers can be remotely compromised for unauthenticated remote code execution, likely exposing sensitive data and authentication domains in many internal and extranet deployments.
Practitioner Perspective
CVE-2026-55040 highlights the risk of high-impact vulnerability chains in widely deployed Microsoft collaboration infrastructure. SharePoint frequently stores business-critical content and, when internet facing or weakly segmented, presents an attractive target for rapid exploitation campaigns. Organizations must recognize that AI-accelerated exploit development is reducing defenders’ response windows on emerging flaws. SharePoint system owners should treat emergency patching and isolation of untrusted interfaces as an urgent operational imperative. Missed patch windows here will inevitably lead to data breaches or loss of domain control.
Recommended Actions
- Apply the official Microsoft patch for CVE-2026-55040 on all affected SharePoint Server installations immediately
- Review access controls and segmentation for SharePoint front-ends, limiting internet exposure wherever possible
OpenAI Launches GPT-5.6-Cyber with Reduced Safeguards for Exploit Development
Source: The Hacker News | Risk: Medium | Impacted: Enterprises with AI/ML research pipelines, Vulnerability management teams, Security tool vendors adopting LLMs
Summary: OpenAI on Monday unveiled a new cybersecurity-focused model called GPT‑5.6‑Cyber that it said is focused on vulnerability research, penetration testing, and incident response. “Built on GPT‑5.6 Sol, it is trained to improve capabilities on several specialized cybersecurity tasks (e.g., finding zero-day vulnerabilities and developing exploit chains) and to reduce refusals for certain higher-risk”.
Why it matters: OpenAI’s release of a model with reduced exploit development safeguards may accelerate the pace and complexity of commodity and bespoke attacks, potentially lowering the expertise required to discover new vulnerabilities or weaponize exploits.
Practitioner Perspective
Specialized AI tooling for security research is a double-edged sword: it empowers blue teams but can immediately amplify adversary automation if misused or accessed by threat actors. Security teams must anticipate faster exploit and vulnerability discovery cycles, especially for zero-days and complex exploit chains. The bar for entry is dropping, so monitoring and defensive research should adapt accordingly, offensive AI techniques are quickly going mainstream. Organizations should track internal and third-party use of AI in their security stack and approach untrusted AI security advisories with skepticism.
Recommended Actions
- Map and monitor use of GPT-5.6-Cyber or similar AI models within internal security workflows
- Review red team and penetration testing guardrails for ethical AI-assisted exploit development
Cisco Patches Firewall Zero-Day Exploited for DoS Attacks
Source: SecurityWeek | Risk: Critical | Impacted: Enterprises using Cisco Secure Firewall ASA, Organizations with Cisco FTD appliances, MSSPs managing multi-tenant Cisco environments
Summary: CVE-2026-20349 can be exploited remotely without authentication against Secure Firewall ASA and FTD devices. The post Cisco Patches Firewall Zero-Day Exploited for DoS Attacks appeared first on SecurityWeek.
Why it matters: Exploitation of CVE-2026-20349 can remotely crash or render Cisco Secure Firewall ASA and FTD devices unavailable, disrupting perimeter security controls and exposing networks to other attacks during downtime.
Practitioner Perspective
This zero-day is already being exploited in the wild against unpatched Cisco firewalls, putting organizations with exposed gateways at imminent risk of denial-of-service or even secondary intrusion during periods of degraded protection. Given the devices’ role as primary network boundary controllers, rapid patching and monitoring is non-optional. Firewall-centric architectures should assume that attackers may combine this DoS with further exploitation or data exfiltration attempts. Ensure robust logging, monitoring, and consider emergency segmentation to sustain protection if outages occur.
Recommended Actions
- Apply Cisco’s security update for CVE-2026-20349 to all affected Secure Firewall ASA and FTD devices as a top priority
- Enable enhanced logging and monitoring for failure or restart events on perimeter firewalls
Defensive Actions
- Immediately review and deploy August 2026 Microsoft security updates, focusing first on issues with confirmed exploitation and public details
- Cross-check all Windows endpoints for patch compliance, especially those running mission-critical services
- Tune web application firewalls and DDoS mitigation services for anomalous HTTP/2 request bursts and malformed patterns identified in Kimwolf v7 reports
- Disable or restrict Zoom annotation features via admin settings on managed clients pending patch application
- Implement targeted phishing simulation training for IT and developer staff focusing on fake recruiter scenarios
- Monitor for known DeadLock ransomware TTPs and be ready to engage with decentralized domains or session-based communications
- Inventory all SIM cards deployed across cellular-connected IoT and OT devices
- Review hash integrity and provenance of Firefox and Thunderbird installers acquired during the affected signing key period
- Implement enhanced verification of candidate identities, especially for remote developer positions in sensitive environments
- Apply Cisco’s security update for CVE-2026-20349 to all affected Secure Firewall ASA and FTD devices as a top priority
What We’re Watching
- Rising exploitation of Microsoft and Cisco zero-days and increased attacker uptake of AI-driven exploit development
- The maturation of social engineering tactics tailored to IT staff and technical teams
- Potential secondary exploitation of trust chains following Mozilla key exposure
- Broader adoption of DDoS and ransomware tactics relying on evasion and decentralization
- Further insider threats and supply chain risks driven by sophisticated social engineering and deceptive onboarding
Categories: Cybersecurity Blog, Cybersecurity News
Leave a Reply