Opens in a new tab

Daily Security Briefing: Thursday, November 12, 2026

  • Home
  • Blog
  • Daily Security Briefing: Thursday, November 12, 2026
Daily security briefing highlighting a ScreenConnect breach targeting MSPs

Quick Answer

Today’s briefing covers 13 security issues reported in the last 24 hours, grouped by type: 3 actively exploited, 2 breaches and data exposure, 4 ransomware and attacks, 3 patches and advisories, 1 scams and phishing. Each entry says who is affected and what to do, with links to the original reports.

Actively Exploited

ScreenConnect Attacks Breach MSPs and Deploy Rogue Remote Access Clients

Who is affected: Huntress said it had identified six compromised MSPs and 286 affected endpoints across 47 organizations, with the number of victims continuing to rise.

They deployed rogue ScreenConnect clients and an SCKit toolkit to provide persistent backdoor access, intercept session cookies and spread through technician sessions. ConnectWise disabled five third-party extensions across approximately 400 partner environments as a precaution and said the presence of those extensions alone does not indicate compromise.

What to do: Disable the listed extensions, ensure security controls are running, preserve suspicious activity logs, and watch for unusual sign-ins, unexpected administrator changes, remote commands and unapproved remote-access software.

Sources: bleepingcomputer.com, thehackernews.com, securityweek.com

Hijacked GitHub Accounts Plant CI Secret Stealer in Repositories

Who is affected: Aikido Security reports that stolen credentials for 4,837 GitHub accounts were used to test 61,764 repositories, while SafeDep counted 8,093 public repositories receiving malicious commits and warned the true total is higher.

Aikido Security detected the “wfx-loot” campaign, in which stolen GitHub credentials opened probe pull requests across 61,764 repositories tied to 4,837 compromised accounts, with malware executing in more than 1,800 repositories. The malware targeted GitHub Actions secrets, cloud credentials, SSH files, shell histories and AI tokens. Affected repositories may include suspicious workflow commits and wfx-docs branches.

What to do: Inspect repositories and cloud accounts for suspicious branches and workflow commits, revoke tokens and sessions, enable two-factor authentication, rotate secrets and investigate for cloud backdoors.

Sources: thehackernews.com, helpnetsecurity.com

N-Able Patches N-Central Vulnerabilities Targeted in the Wild

Who is affected: N-able said all on-premises N-central deployments should be updated as soon as possible, as attackers are already probing exposed instances.

N-able patched the vulnerabilities that could be exploited without authentication and brought hosted environments back online. Remaining vulnerabilities require an authenticated account, elevated privileges or additional conditions and are to be addressed through subsequent hotfixes.

What to do: Update all on-premises N-central deployments to N-central 2026.4 HF2 as soon as possible.

Sources: securityweek.com

Breaches and Data Exposure

Baker Tilly Reports Data Breach Involving a Third-Party Service Platform

Who is affected: The Office of the Texas Attorney General reports that Baker Tilly impacted 10,456 individuals in Texas, while the breach notification does not provide a count of impacted clients.

An unauthorized actor obtained data relating to certain Baker Tilly clients from a platform operated by a third-party service provider. Baker Tilly said it learned of the incident on September 6 and completed its review of the affected data on October 28. The Office of the Texas Attorney General lists Social Security numbers, full names, addresses and other information as exposed data types. The firm says it has no evidence of unauthorized activity on its own network or reports of identity theft or fraud linked to the exposure.

What to do: Review the breach notification.

Sources: bleepingcomputer.com

Fireworks AI Breach Exposes Some Notion AI Chat Transcripts

Who is affected: Notion’s investigation determined that the hackers accessed Notion AI chat transcripts used for the Insights feature. Notion says fewer than 1% of Notion workspaces were affected and most of the transcripts were unattributable to a customer or the workspace they came from.

Fireworks AI was hacked twice in October: once through compromised internal credentials, and once through a third-party cloud provider that was hosting Fireworks R&D machines. The second incident occurred on October 24, when the attackers executed an unauthorized workload leading to the compromise of customer data. Fireworks contained the incident the same day and notified Notion on November 2 that Notion AI data had been accessed. Notion has contacted the affected customers but has not disclosed how many were affected.

What to do: Notion recommends treating this data as exposed and rotating any exposed credentials if sensitive information, passwords, API keys or other credentials were pasted into Notion AI during the incident.

Sources: securityweek.com

Ransomware and Attacks

Maersk Confirms Data Theft From an Acquired Business System

Who is affected: Maersk confirmed data was extracted from one IT system inherited through an earlier acquisition, without identifying the acquired business.

According to SecurityWeek, the WhiteArmor ransomware group claims it stole 100GB of data from the shipping giant’s systems and is demanding $5 million. Maersk says its investigation found the incident isolated to a local system, with no indication of impact on other company, customer or partner systems, and that its findings so far strongly suggest no sensitive data was disclosed. The group’s claims have not been independently verified, and Maersk has not disclosed the intrusion date, access method or types of data taken.

Sources: securityweek.com

Threat Actors Abuse GSocket for Persistent Access to Linux Servers

Who is affected: Linux servers targeted through web applications and hosting environments are affected, with education and research, technology, communications and manufacturing among the most targeted sectors.

Attackers installed the legitimate GSocket remote access tool to maintain access after patching the vulnerabilities used for initial access. GSocket routes outbound connections through a relay, allowing reconnection without the compromised server’s IP address or hostname and making inbound access controls less effective.

What to do: Monitor outbound traffic for GSocket-related connections and investigate unexpected outbound relay activity.

Sources: bleepingcomputer.com

Threat Actor Used AI Commands During Attack on US Retailer

Who is affected: An unnamed US retail organization was targeted in September.

Hand-typed commands were repeatedly blocked, so the threat actor switched to apparent AI-generated commands and broke through the retailer’s defenses. The attacker harvested credentials and achieved lateral movement within minutes, with investigators believing an operator relayed output to an AI tool rather than using an autonomous agent.

What to do: Review credential use and lateral movement across systems after an intrusion.

Sources: darkreading.com

Stolen Claude API Keys Enable Remote Control of Claude Code

Who is affected: Darktrace researchers said an attacker would first have to compromise a developer’s machine and obtain the user’s Claude credentials.

Darktrace researchers turned Claude Code into a remote-controlled implant in a lab test, steering the coding agent through the memory stores feature of Anthropic’s Claude platform and pulling a 1 GB file out through the Claude Files API. The test ran on a simulated corporate Active Directory network. The operator sent nine jobs through the memory store. The agent mapped the local network, pulled employee names and a password from an anonymous FTP share, generated 190 candidate usernames, and sprayed the password at the domain controller and found the account it belonged to. It listed SMB shares with that account, downloaded a 1 GB file, split it into three pieces, and uploaded them to the Files API. The technique does not rely on a Claude platform vulnerability, and the company has not seen it used in the wild.

Sources: helpnetsecurity.com

Patches and Advisories

Apache Fixes HTTP/2 Flaw Allowing Remote Code Execution

Who is affected: According to Red Hat, only servers with HTTP/2 enabled are affected. The flaw affects Apache HTTP Server versions 2.4.55 through 2.4.70, and standalone mod_h2 versions 2.0.8 through 2.0.42.

According to Red Hat, CVE-2026-119618 can let a remote attacker who can reach the server run code without authentication and could take full control of the server process. Red Hat rates the flaw 9.8 out of 10 on the CVSS scale and says “public research has demonstrated a reliable exploit” against a server in its default configuration with mod_http2 enabled. Wiz said later that no exploit was available and that no exploitation in the wild had been reported. The flaw is fixed in Apache HTTP Server version 2.4.71, and Red Hat shipped fixes for Red Hat Enterprise Linux 9 and 10.

What to do: Upgrade Apache HTTP Server to the fixed release or install the applicable distribution package, and check both server-wide and virtual host HTTP/2 settings.

Sources: thehackernews.com, thehackernews.com

Red Hat Quay Flaw Could Expose Private Container Images

Who is affected: Organizations using Red Hat Quay in deployments where the service responsible for managing signing keys is accessible to untrusted clients are affected.

An unauthenticated attacker could take over registry token signing, install a trusted signing key and generate tokens granting read and write access to any repository. This could expose private images and secrets stored in them, overwrite images and interfere with registry operations. Disabling anonymous access, changing passwords or regenerating robot tokens does not invalidate an unauthorized signing key.

What to do: Restrict access to the key-management service, review logs for suspicious key changes and remove unauthorized keys.

Sources: securityweek.com

MongoDB Pre-Auth Flaw Can Crash Lagging Servers on Failover

Who is affected: Vulnerable replica set members, including shard and config server members of sharded clusters, are affected; standalone mongod servers are not affected.

Two requests can trigger a use-after-free crash, but the targeted server must later be selected as the main server while it still lacks recent changes. Authentication does not stop the requests, and Atlas clusters receive fixed versions during maintenance.

What to do: Apply the fixed release to every self-managed replica set member and check that each member is running the fixed version.

Sources: thehackernews.com

Scams and Phishing

UK Retailers Face Increased Intrusions During Peak Trading Periods

Who is affected: UK retailers and online stores face increased intrusion attempts, with attacks rising 169% year over year and most attacks targeting web applications.

SonicWall recorded 23.3 million high- and medium-priority intrusion attempts and almost 400,000 malware attacks between January and September 2026. Most attacks targeted web applications through techniques including directory traversal, remote code execution and cross-site scripting. Stolen customer data from retail breaches can be used for phishing, fraud and follow-on attacks.

What to do: Review web application security and prepare to identify and respond to phishing and fraud attempts during the peak trading period.

Sources: techradar.com

This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.

Sources

← All Articles