Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7

Arch Linux halts package adoptions after infostealer floods the user repository

The Arch Linux project temporarily disabled adoption of packages in its user repository, the AUR, after a wave of malicious takeovers of existing packages. Attackers seized packages through compromised maintainer accounts or by adopting orphaned ones, then shipped a Rust-based infostealer that grabs browser credentials, cryptocurrency wallets, password manager data, cloud and developer secrets, AI service API keys, and SSH keys. It also opens remote command execution over an encrypted Tor channel and spreads to other machines using stolen SSH keys. A researcher tracking the campaign claims more than 200 packages were hit, including some popular ones, though that list is not independently confirmed.

Check
If you use the AUR, review recently installed or updated packages and their maintainers, inspect build files before installing, and rotate SSH keys and secrets if you ran a suspect package.
Affected
Arch Linux users who install from the AUR; a hijacked or adopted package can run a Rust infostealer that harvests developer, cloud, and AI credentials and SSH keys, then self-spreads.
Fix
Read AUR build scripts before installing, prefer well-maintained packages, rotate exposed credentials and SSH keys, watch for outbound Tor connections, and treat orphaned or newly adopted packages with particular caution.

Attacker wires DeepSeek into an agent to hunt and exploit exposed servers

Palo Alto Networks Unit 42 detailed a Chinese-speaking attacker who used the DeepSeek model as the reasoning engine inside an open-source agent called Hermes to attack exposed servers with little human input. Taking instructions over Telegram and using an internet asset search engine, the agent ran in a mode that executes commands without asking permission: from a single task, it downloaded a public exploit, enumerated vulnerable Langflow and n8n instances, judged targets by value, and attempted exploitation on its own. The autonomous attempts failed, blocked by authentication and configuration, though the operator succeeded manually elsewhere. The operation was exposed when the agent accidentally served its own working directory over the web.

Check
Keep self-hosted tools like n8n and Langflow patched, authenticated, and off the public internet, since autonomous agents now scan asset search engines and attempt exploitation without a human in the loop.
Affected
Organizations exposing self-hosted AI and automation tools such as Langflow and n8n; autonomous AI agents can discover, rank, and attack them at scale, though basic authentication and hardening blocked the observed attempts.
Fix
Require authentication, disable risky auto-login options, restrict management interfaces, and patch known flaws, since the defensive configurations that stopped this agent are the same controls that blunt automated exploitation generally.

Azure Cosmos DB flaw exposed a master key that unlocked every customer database

Wiz Research disclosed CosmosEscape, a critical flaw chain in Microsoft's Azure Cosmos DB that could have given an attacker read and write access to every customer database on the service, including Microsoft's own. Starting from a crafted query against an attacker-controlled Gremlin database, the researchers escaped the query sandbox using .NET reflection, ran code on a shared gateway, and retrieved a platform-wide signing secret they call the Cosmos Master Key. That key let them fetch the access key for any Cosmos DB account on demand, reaching even private, network-isolated databases. Microsoft assigned CVE-2026-66803, fixed the issue across all regions, and found no evidence of abuse. Nothing needs patching by customers.

Check
No customer patching is required since Microsoft fixed this in the service, but review Cosmos DB access logs for unusual activity and consider rotating account keys as a precaution.
Affected
Azure Cosmos DB customers using the Gremlin API were at risk while the flaw was live; the exposed master key could reach any account's data across tenants, though Microsoft reports no abuse.
Fix
Treat this as a reminder that multi-tenant cloud isolation can fail: rotate Cosmos DB keys periodically, prefer short-lived credentials and network limits, and monitor database access.

Critical TeamCity flaw lets unauthenticated attackers run commands on the CI server

JetBrains patched a critical flaw in TeamCity, its continuous integration and delivery server, that lets an unauthenticated attacker run operating-system commands. Tracked as CVE-2026-63077 and scored 9.8, the deserialization bug affects all on-premises versions and is reached through the agent polling protocol, letting an attacker with HTTP access bypass authentication and execute commands with the privileges of the server process. JetBrains warns that exploitation exposes stored credentials and can compromise the integrity of the build pipeline. It is fixed in versions 2025.11.7 and 2026.1.3, with a patch plugin for older releases, and TeamCity Cloud is already updated. No exploitation has been reported.

Check
Upgrade on-premises TeamCity to 2025.11.7 or 2026.1.3, or apply the security patch plugin if you cannot upgrade, and restrict network access to the server.
Affected
Organizations running any on-premises TeamCity version (CVE-2026-63077); an unauthenticated attacker with HTTP access can execute commands as the server process, steal stored credentials, and tamper with build pipelines.
Fix
Patch or apply the plugin, keep TeamCity off the public internet or behind a VPN, rotate credentials the server held, and review build configurations and logs for unauthorized changes.

Chipmaker Analog Devices confirms a breach and stolen files, says operations are fine

Analog Devices, a major US semiconductor maker, confirmed in a securities filing that an unauthorized party accessed some internal systems and exfiltrated files in a June intrusion, while saying operations were not affected. The company has not named who was responsible. Days before the filing, an extortion group calling itself ExfilSquad listed Analog Devices on its leak site and claimed to hold about 570,000 customer records with personal information and home addresses, but Analog Devices has not linked the June breach to that group, and the claim is unverified. The filing also noted a second, separate security issue unrelated to the June intrusion.

Check
Organizations that share data with Analog Devices should watch for a notification and monitor for phishing, while treating the extortion group's specific claims as unverified until the company confirms details.
Affected
Analog Devices and parties whose data sat in its systems; the company confirms files were stolen in June, while an extortion group's claim of 570,000 customer records with home addresses remains unverified.
Fix
Affected parties should watch for official notice and be alert to targeted phishing. Organizations should segment sensitive data, limit what vendors can reach, and prepare for extortion-driven leaks and unverified claims.

Hidden text in a Word file makes Copilot alter data and spread the payload

A researcher disclosed a prompt-injection technique that turns Microsoft 365 Copilot for Word into a carrier for self-spreading instructions. Malicious commands hidden as tiny white-on-white text in a document are invisible to a reader but read in full by Copilot when the file enters its context during a drafting or editing task. Copilot then follows them, in one example silently altering financial figures in a report, and copies the same hidden instructions into the new document, which becomes a fresh carrier for the next person who uses it. It does not spread on its own, but Microsoft's mitigations over 144 days blocked specific wordings without fixing the underlying class.

Check
Treat documents from outside as untrusted input to AI assistants, and review how Copilot and similar tools are used on shared or externally sourced files that may carry hidden instructions.
Affected
Organizations using Microsoft 365 Copilot for Word on documents from outside sources; hidden instructions can make Copilot tamper with content, such as financial figures, and propagate into newly created files.
Fix
Limit AI drafting on untrusted documents, review AI-edited outputs for unexpected changes, strip hidden text from incoming files, and press vendors for controls that separate document content from instructions.

Amazon ties the chalk and debug npm hijacks to North Korean hackers

Amazon's threat intelligence team linked several major npm supply chain attacks to a North Korean group tracked as Sapphire Sleet, also known as BlueNoroff. The group compromised the small typo-crypto package in March 2025 as a test, then hijacked the hugely popular debug and chalk packages in September 2025, and axios in March 2026. The debug and chalk incident, which pushed a wallet-draining script into packages with billions of weekly downloads, reached roughly one in ten cloud environments within two hours. The attackers gained access by phishing package maintainers through lookalike npm domains, then published malicious versions that auto-installing projects pulled in.

Check
Review whether your projects or CI pulled compromised versions of typo-crypto, debug, chalk, or axios during the affected periods, and check developer and build environments for wallet-draining or credential-stealing behavior.
Affected
Developers and organizations that auto-install npm dependencies; a phished maintainer account can push a malicious version of a hugely popular package that reaches thousands of downstream environments within hours.
Fix
Pin and verify dependencies, add a delay before adopting new versions, watch for maintainer-account phishing, protect publishing accounts with phishing-resistant MFA, and monitor build environments for credential and wallet theft.

Fake IT support calls on Microsoft Teams end in Chaos ransomware

Sophos detailed a campaign, tracked as STAC4749, in which attackers impersonate IT help desk staff over Microsoft Teams to talk employees into granting remote access, then deploy Chaos ransomware. Using external Teams accounts, the operators start chats and voice calls claiming to fix an urgent problem, persuade the target to open a remote support session, and run PowerShell to pull down a modular toolkit for persistence and lateral movement. Between February and June 2026 they hit dozens of North American organizations, about 95 percent in the US and Canada, across services, manufacturing, energy, and construction. In one case they went from first contact to encrypting files in under seventeen hours.

Check
Restrict or block messages and calls from external Microsoft Teams accounts, and tell staff that real IT support will not cold-call them over Teams to request remote access.
Affected
North American organizations whose staff can be reached by external Teams accounts; attackers posing as IT support talk employees into remote access, then move laterally and deploy Chaos ransomware, sometimes within hours.
Fix
Lock down external Teams contact, train staff to verify support requests through known channels, monitor for unexpected remote-access tools and suspicious PowerShell, and audit startup and registry entries for persistence.

Cisco patches exploited Firewall Management Center flaw that grants built-in account access

Cisco has patched a flaw in Secure Firewall Management Center that attackers were already exploiting to log into devices. Tracked as CVE-2026-20316, it stems from static credentials for a low-privilege account built into the software, letting an unauthenticated remote attacker sign in and read sensitive data. Cisco scored it 5.3 but rated it High because the access can be chained with other flaws to escalate privileges. In the same cycle it patched CVE-2026-20079, a separate critical authentication bypass that reaches root, and shipped one set of hot fixes with a shared indicator suggesting the two could be combined. There are no workarounds.

Check
Upgrade Secure FMC to a fixed release now, and check for compromise by searching device logs for references to /var/tmp/license.tmp, which Cisco lists as an indicator.
Affected
Organizations running Cisco Secure Firewall Management Center releases 7.0, 7.2, 7.4, 7.6, 7.7, or 10.0 (CVE-2026-20316); the flaw is exploited, and chaining with the root-level bypass raises the stakes.
Fix
Apply Cisco's hot fixes, since there is no workaround, keep the FMC management interface off the public internet, and if the indicator appears, rotate all device credentials, keys, and certificates.

Russian actor exploits Outlook Web Access flaw for mailbox access that survives resets

Proofpoint reported a Russia-aligned group, tracked as Laundry Bear or TA488, exploiting a cross-site scripting flaw in on-premises Outlook Web Access to plant a stealthy backdoor. Tracked as CVE-2026-42897 and rated 8.1, it is a half-click exploit: opening a crafted email in OWA runs attacker JavaScript in the session. The implant, OWAReaper, steals OAuth tokens from mailbox add-ins and grants the low-privilege Default user Owner rights on every mail folder, so any account in the organization can read the mailbox. Because that grant lives on the Exchange server, rotating credentials and re-imaging the device do not remove the access. Microsoft flagged exploitation since May.

Check
Confirm on-premises Exchange has the fix for this flaw, then audit mailbox folder permissions for Owner rights wrongly granted to the Default user, and review add-ins with mailbox write access.
Affected
Organizations running on-premises Exchange Outlook Web Access (CVE-2026-42897); opening a crafted email runs attacker code, and the backdoor's server-side permission grant keeps access alive through credential resets and re-imaging.
Fix
Patch, then remove the malicious folder-permission grants and audit add-ins with mailbox write access, since patching alone does not evict the attacker, and hunt for OWAReaper artifacts and unusual token use.