Infosec News

cyclone

Verizon Nationwide Outage (Jan. 14, 2026)

Verizon Communications experienced a major nationwide wireless network outage beginning around midday on January 14, 2026, disrupting voice, text, and mobile data services across the United States for approximately ten hours. Customers reported their phones showing “SOS” or “SOS-only” status in place of normal signal bars, indicating loss of cellular connectivity.

Outage monitoring sites such as DownDetector logged hundreds of thousands of reports at the peak, with impacts reported coast-to-coast in major metropolitan areas including New York City, Chicago, Boston, Atlanta, Dallas, and others. Some local officials warned that emergency calls (911) for Verizon users could be unreliable during the disruption, recommending alternatives such as landlines or other carriers where possible.

Verizon acknowledged the outage via social media and later confirmed that service was restored late Wednesday night. The company apologized for the interruption and stated it will issue account credits to affected customers. Verizon did not immediately disclose a specific technical cause, though internal reviews are expected.

The Federal Communications Commission (FCC) indicated it would review the outage’s impact on network reliability and public safety communications.

Sources:

cyclone

Atomic Wallet - Where Did My XMR Go?

Many Atomic Wallet users recently logged in to find their Monero (XMR) balances missing or incorrect, causing understandable concern.

According to Atomic Wallet support, this is a display and synchronization issue specific to Monero, not a loss of funds. Atomic states that all XMR remains safe on-chain and that their development team is working on a fix. Once synchronization is corrected, balances and transaction history should update normally.

Users can independently confirm their funds by restoring their XMR wallet in another trusted Monero wallet using their existing keys or seed phrase. Multiple users report that their full balances appear correctly when checked outside Atomic, confirming the issue is isolated to Atomic’s wallet interface.

Given Atomic Wallet’s 2023 security breach, users are understandably cautious. While this situation appears unrelated and no theft has been reported, verifying balances independently is recommended.

Summary

Issue affects XMR balance display in Atomic Wallet
Funds are still on-chain and under user control
Atomic says a fix is in progress
Users can verify funds using another Monero wallet
Use caution, verify independently, and never share your private keys or seed phrase with anyone

Sources:

@cyclone (independent verification with Atomic)
https://x.com/AtomicWallet/status/2011796132112826643

oe3p32wedw

haahahahahah

cyclone

Ivanti EPMM Zero-Day RCE - CVE-2026-1281 & CVE-2026-1340

Ivanti has disclosed two critical zero-day vulnerabilities in Ivanti Endpoint Manager Mobile (EPMM), tracked as CVE-2026-1281 and CVE-2026-1340. Both flaws are unauthenticated code injection issues that allow remote attackers to achieve arbitrary code execution on affected EPMM appliances. Active exploitation has been confirmed, and CVE-2026-1281 has been added to CISA’s Known Exploited Vulnerabilities catalog.

The vulnerabilities affect EPMM 12.x versions prior to 12.8.0.0 and are tied to In-House Application Distribution and Android File Transfer Configuration features. Successful exploitation grants full control over the EPMM appliance, enabling attackers to establish persistence, access sensitive mobile device management data, and potentially pivot into connected enterprise environments.

Ivanti has released interim RPM-based patches, though these must be reapplied after upgrades. A permanent fix is scheduled for EPMM 12.8.0.0. Organizations are strongly advised to apply mitigations immediately, review logs for signs of exploitation, and treat exposed EPMM instances as high-risk assets.

Source:

https://thehackernews.com/2026/01/two-ivanti-epmm-zero-day-rce-flaws.html

cyclone

Notepad++ Supply Chain Compromised

What Happened

Notepad++ was involved in a supply chain compromise where parts of its update delivery infrastructure were breached. The application’s source code was not modified, but attackers were able to tamper with the update distribution path for a limited period. In targeted cases, users running older versions and using the built-in updater could have been redirected to malicious installer binaries hosted on attacker-controlled infrastructure.

The campaign appears to have been highly targeted rather than mass exploitation, consistent with espionage-style activity. The issue was identified and remediated after the Notepad++ team migrated infrastructure and tightened update security.

Impact

Risk was limited primarily to older Notepad++ versions using legacy update mechanisms.
Users who did manual downloads from trusted mirrors were unlikely to be affected.
No evidence suggests the official source repository itself was compromised.

What Users Should Do

Update immediately to the latest Notepad++ version using a fresh manual download from the official site or trusted mirrors.
Verify digital signatures and hashes of the installer before execution.
If Notepad++ was updated automatically during the affected timeframe:
- Treat the system as potentially exposed.
- Run endpoint security scans.
- Review network logs for suspicious outbound connections.
Enterprise environments should audit systems where Notepad++ is installed and consider blocking auto-updaters that lack strict signature validation.

Sources:

cyclone

Windows Notepad Remote Code Execution - CVE-2026-20841

Summary

Not to be outdone by the recent Notepad++ RCE, the Windows Notepad CVE-2026-20841 is a high-severity remote code execution (RCE) vulnerability affecting the modern Windows Notepad application. The issue was introduced after Microsoft added Markdown and rich link support to Notepad.

The vulnerability stems from improper sanitation of special elements within commands, effectively allowing command injection via crafted Markdown links.

Technical Details

An attacker can craft a malicious .md file containing a specially constructed link. When a user opens the file in Notepad and Ctrl-clicks the link, the application may invoke external protocols or executables without sufficient validation or security warnings.

Successful exploitation allows arbitrary code execution in the context of the logged-in user.

Key Characteristics

Type: Remote Code Execution
Vector: Malicious Markdown file with crafted link
User Interaction Required: Yes (file open + link click)
Privileges Gained: Same as current user
Attack Surface: Expanded via Markdown rendering and clickable links

Impact

If exploited, an attacker could:

Execute arbitrary binaries
Download and run malware
Establish persistence
Perform lateral movement (depending on user privileges)

However, there were no confirmed in-the-wild exploits at the time of disclosure.

Remediation

Microsoft addressed the vulnerability in the February 2026 Patch Tuesday updates for the Windows 11 Notepad flaw by displaying warnings when clicking a link if it does not use the http:// or https:// protocol.

Sources:

cyclone

Chrome CSS Zero-Day (CVE-2026-2441) – Active Exploitation Confirmed

Google has released an emergency security update for Chrome after confirming active exploitation of a high-severity zero-day vulnerability in the browser’s CSS handling engine.

The flaw, tracked as CVE-2026-2441, is a use-after-free memory corruption issue in Chrome’s CSS parsing/rendering component. Although CSS is generally considered non-executable, improper memory management allows attackers to craft malicious webpages that can trigger arbitrary code execution within the Chrome renderer process.

Key Details:

Type: Use-after-free (memory corruption)
Component: Chrome CSS engine
Severity: High (CVSS ~8.8)
Exploitation: Confirmed in the wild
Impact: Remote code execution via malicious webpage

Successful exploitation requires a victim to visit a specially crafted website. While Chrome’s sandbox limits direct system access, attackers often chain renderer bugs with sandbox escapes for full compromise.

Google has patched the issue in the latest stable release. All users, especially enterprise environments and those running Chromium-based browsers (Edge, Brave, Opera), should update immediately.

Sources:

freeroute

New AirSnitch attack breaks Wi-Fi encryption in homes, offices, and enterprises
That guest network you set up for your neighbors may not be as secure as you think.

To prevent malicious Wi-Fi clients from attacking other clients on the same network, vendors have introduced
client isolation, a combination of mechanisms that block direct communication between clients. However, client isolation is not a standardized feature, making its security guarantees unclear.

Source: New AirSnitch attack breaks Wi-Fi encryption in homes, offices, and enterprises
Github: https://github.com/vanhoefm/airsnitch
AirSnitch: Demystifying and Breaking Client Isolation in Wi-Fi Networks

cyclone

Gemini Access to Unintended Public Google Cloud API Keys

Recent research by Truffle Security identified 2,863 publicly exposed Google Cloud API keys that can authenticate to Google Gemini endpoints following API enablement. These keys, commonly embedded in client-side JavaScript for benign services such as maps and analytics, were not originally intended for AI access.

When the Gemini (Generative Language) API is enabled within a Google Cloud project, all existing API keys in that project inherit access by default, including publicly exposed keys. This creates a significant risk of unauthorized data access and quota abuse.

Key Findings

API keys with the prefix AIza were found embedded in public-facing code
Enabling the Gemini API retroactively grants those keys access to AI endpoints
Newly created API keys default to “Unrestricted”, allowing access to all enabled APIs
Attackers can:
- Access /files and /cachedContents endpoints
- Execute Gemini API calls
- Generate excessive LLM usage charges
One reported case alleged $82,314.44 in unauthorized charges within 48 hours

A separate scan by Quokka identified over 35,000 Google API keys embedded across 250,000 Android applications, indicating broader ecosystem exposure.

Risk Impact

This issue transforms what were historically treated as low-risk billing identifiers into high-value AI credentials.

Potential consequences include:

Data exposure via AI-related endpoints
API quota theft and financial loss
Expanded blast radius through AI-integrated cloud services
Elevated abuse potential due to generative AI capabilities

The behavior was initially considered intended functionality. Google has since implemented proactive controls to detect and block leaked API keys attempting Gemini access. No confirmed exploitation campaigns have been publicly reported at this time.

Recommended Actions

Organizations using Google Cloud should:

Audit enabled APIs in all projects
Identify and rotate exposed API keys immediately
Prioritize older keys deployed under previous guidance
Restrict API keys to specific services and referrers
Remove API keys from client-side code where possible
Implement continuous API monitoring and anomaly detection

Sources:

cyclone

Active Exploitation of Cisco Catalyst SD-WAN CVSS 10.0 Zero-Day (CVE-2026-20127)

Overview

Security researchers and government agencies have confirmed active exploitation of a critical vulnerability affecting Cisco Catalyst SD-WAN infrastructure. The vulnerability, tracked as CVE-2026-20127, allows an unauthenticated remote attacker to bypass authentication on affected Cisco Catalyst SD-WAN Controller and Manager systems and gain administrative access.

The flaw carries a CVSS score of 10.0 (critical) and enables attackers to send crafted requests to the SD-WAN controller, resulting in login access as a high-privileged internal account. Once initial access is obtained, the attacker can manipulate SD-WAN network configuration and potentially gain full control of the platform.

Cisco Talos attributes the activity to a sophisticated threat cluster tracked as UAT-8616. Investigation indicates that exploitation activity has likely been occurring since at least 2023, meaning organizations may have been compromised for several years before disclosure.

Exploitation Chain

Observed attacks follow a multi-stage compromise process:

Initial Access
- Exploitation of CVE-2026-20127 allows authentication bypass on Cisco Catalyst SD-WAN controllers.
- Attackers gain administrative access as a privileged non-root user.
Privilege Escalation
- Attackers downgrade the SD-WAN software to reintroduce CVE-2022-20775, a CLI path traversal vulnerability.
- This allows escalation from administrative access to root privileges.
Persistence and Covering Tracks
- After obtaining root access, attackers restore the system to the original software version to conceal the downgrade.
- The actor establishes persistence through:
  - Unauthorized SSH keys
  - Creation and deletion of local user accounts
  - Modification of startup scripts
  - Rogue SD-WAN control connections
- Logs and command histories are frequently cleared or truncated to reduce forensic evidence.

Observed Post-Compromise Activity

Investigations identified several behaviors associated with successful compromise:

Addition of rogue SD-WAN control peers to the network fabric.
Creation of malicious or impersonated local user accounts.
Deployment of unauthorized SSH keys in:
- /home/root/.ssh/authorized_keys
- /home/vmanage-admin/.ssh/authorized_keys
Enabling root SSH login by modifying SSH configuration.
Clearing or truncating logs including:
- syslog
- wtmp
- lastlog
- cli-history
- bash_history
Unexplained software version downgrades followed by re-upgrades.
Unusual control-plane peering events originating from unknown IP addresses.

Threat actors also leveraged NETCONF (port 830) and SSH to move laterally between SD-WAN components within the management plane.

Impact

Cisco Catalyst SD-WAN components operate within the network control plane and manage connectivity between distributed sites and cloud environments. Compromise of these systems can allow attackers to:

Modify routing and network policies
Intercept or redirect traffic
Maintain persistent access to enterprise networks
Use the SD-WAN fabric as a foothold for broader compromise

Organizations operating internet-exposed SD-WAN management interfaces are considered at highest risk.

Government and Industry Response

Multiple government cybersecurity agencies issued joint advisories warning of ongoing exploitation. U.S. federal agencies were directed to immediately inventory and patch affected SD-WAN deployments due to the risk posed to critical infrastructure and government networks.

The vulnerability has been added to the Known Exploited Vulnerabilities (KEV) catalog, requiring rapid remediation within federal environments.

Detection and Threat Hunting Guidance

Defenders are advised to investigate:

Unexpected SD-WAN control-plane peering events
Unknown public IP addresses establishing controller connections
Root logins or SSH key changes on SD-WAN nodes
Missing or abnormally small log files
Evidence of temporary software downgrades followed by re-upgrades

Manual validation of control connection events in SD-WAN logs is considered a critical indicator of potential exploitation.

Mitigation

Recommended defensive actions include:

Immediately applying Cisco patches for affected SD-WAN components.
Reviewing controller logs for unauthorized peering connections.
Restricting access to management interfaces and SD-WAN control ports.
Blocking unnecessary internet exposure of SD-WAN controllers.
Implementing Cisco’s SD-WAN hardening guidance and continuous log monitoring.

Organizations are strongly advised to assume potential compromise if indicators described in the advisories are present.

Sources:

hashpwn

Infosec News

What Happened

Impact

What Users Should Do

Summary

Technical Details

Key Characteristics

Impact

Remediation

Sources:

Key Findings

Risk Impact

Recommended Actions

Overview

Exploitation Chain

Observed Post-Compromise Activity

Impact

Government and Industry Response

Detection and Threat Hunting Guidance

Mitigation

Who's Online [Full List]

Board Statistics