Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Ransomware Group Wiped an Entire VMware Estate in Ten Days Without Exploiting a Single Vulnerability




A ransomware group called BlackNevas dismantled a company's entire virtualization infrastructure over ten days, destroying four ESXi hosts, every virtual machine running on them, two vCenter Server Appliances, and the backup systems meant to recover from exactly this kind of attack. The findings, published by Kaspersky's Global Emergency Response Team, detail how attackers moved through one of the most common enterprise environments without triggering a single exploit alert, because they never used one.

The core finding is uncomfortable for organizations that have treated patching as the main line of defense: every action the attackers took against ESXi ran through legitimate VMware management interfaces. The group obtained valid administrative credentials, used VMware's own tools to push configurations, and triggered ransomware detonation through supported remote access channels.

Ransomware made up 39.4 percent of all incidents Kaspersky's response team handled in 2025. The ESXi segment of that is growing, partly because of a decision made in 2021. When the Babuk ransomware source code leaked, it included a working ESXi version, and at least ten ransomware families have since reused that codebase. BlackNevas is one of them.


How the Attack Unfolded

BlackNevas, first observed in November 2024 and also tracked as a Trigona family variant, operates across Windows, Linux, NAS devices, and ESXi hypervisors. The group runs double extortion, stealing data before encrypting it and threatening public leaks to pressure victims. Known targets include organizations in healthcare, finance, manufacturing, legal services, and telecom across Asia, Europe, and North America.

In this incident, the attackers got in through credential reuse. Valid administrative credentials from non-virtualization systems were used to reach the vCenter Server Appliances, which manage the ESXi hosts. This is the same access path defenders often overlook because they focus on preventing vulnerability exploitation rather than limiting what happens when credentials are already compromised.

Forty-three seconds after logging into the VCSA via SSH as root, the attackers deployed MeshAgent, part of the open-source MeshCentral remote management platform. The entire SSH session lasted two minutes and 26 seconds. Four hours later, they returned through MeshAgent and installed Ligolo-ng, a tunneling tool, as a systemd service disguised under the name `vmware-vdma.service` to blend in with legitimate VMware components.

The next step exploited a feature few organizations think to restrict. VMware's Host Profiles allow administrators to push consistent configurations to ESXi hosts from vCenter. The attackers used this to enable Tech Support Mode SSH across the hosts. Ten minutes and 18 seconds after the configuration was pushed, the TSM-SSH service was running. SSH sessions to ESXi then originated from the vCenter appliance IP, which most environments treat as a trusted internal source.


Taking Out Backups First

Before touching the ESXi layer, the attackers disabled antivirus on the backup infrastructure, stopped backup services, and encrypted the recovery systems. This sequence is deliberate. Ransomware operators have learned that organizations with clean backups can often recover without paying, so the backup environment is now treated as part of the primary attack surface.

Two Veeam vulnerabilities are worth noting here. CVE-2024-40711, which CISA has added to its Known Exploited Vulnerabilities catalog, has been directly linked to ransomware campaigns. CVE-2025-23120 is not on that list yet, but affects domain-joined backup servers and represents a less-patched exposure in many environments.


Detonation and Partial Recovery

The ransomware payload was uploaded to ESXi hosts via SFTP. Roughly three hours before detonation, it ran a self-test lasting about 16 seconds. The final command processed virtual machine storage directories with options to wipe and detach volumes. On one host, all virtual machines stopped within 23 seconds. The ransomware overwrote approximately the first two kilobytes of virtual disk files. Kaspersky notes that a valid backup GPT header may allow partial recovery in some cases, though this is not a reliable path.

A crucial detection problem runs through the entire attack. ESXi writes logs to a RAM disk by default, meaning a reboot erases them. If forensic investigators arrive after a reboot, the evidence of how attackers moved through the environment is gone. Kaspersky recommends configuring remote syslog to preserve ESXi logs outside the virtualization trust domain.


What Organizations Should Change

Kaspersky's recommendations center on treating vCenter as a Tier 0 asset, the same classification given to domain controllers. That means separate administrative identities for virtualization management, phishing-resistant multi-factor authentication, and limiting SSH and ESXi Shell access through Lockdown Mode. Network filtering on the management interface, combined with logs stored outside the virtualization environment, closes the two gaps this attack exploited most effectively.

The practical lesson from this incident is that a patched VMware environment is not a protected one if the credentials managing it are shared with less-secured systems.



Meta Fined €805 Million in Italy Over Facebook’s Access to Android Photo Galleries Without Consent

 

Meta has been fined €805 million by Italy’s data protection authority for using the gallery suggestions feature on Facebook, which was activated by default, to access users’ images, videos and metadata. 

The Italian Data Protection Authority (Garante) has told Meta to remove the feature from being active by default. This means that it will need to ensure the feature does not appear as an active option for users who have previously allowed access to their phone galleries. It will also need to make sure that the feature cannot be used without an additional opt-in, with clear information about what the feature does and how to turn it off. 

During the investigation it was discovered Facebook had used a blanket permission to give access to multiple functions within the app. There was no clear explanation to users that the permission would allow the app to suggest photos and videos from their private galleries. Once users had given the permission Facebook could gain access to a whole photo album. The authority said it was difficult to know exactly what information the application was gaining access to. 

Garante concluded that this breached Article 122 of the Italian Privacy Code. This article was introduced to bring the ePrivacy Directive of the European Union into national law. It means that any information stored on users’ devices as part of their private life must be given free and informed consent before applications are allowed to access it. Meta has appealed the fine. A spokesperson said the fine was unfair as the feature cannot be used unless users have allowed it in their device settings. They added that users can revoke or change their permission at any time. 

The authority has also told Meta that it must provide an initial report on how it will comply with the ruling within 30 days and a final report within 90 days. If they fail to comply within the 60-day timeframe then the feature cannot be active for users who haven’t given valid consent. This comes after a complaint from consumer protection organisation Centro Tutela Consumatori Utenti in Bolzano. In July 2025, they advised users of Facebook to turn off the gallery suggestions and check the app’s permissions. The investigation did not look into whether the content from Facebook’s galleries were used to train AI models. Meta has denied this. 

However, Garante may investigate whether the new feature introduced this year, which allows processing of gallery content in the cloud, has breached any rules. Meta had claimed that the Irish data protection regulator should be responsible for this issue. However, this was rejected by Garante as the ePrivacy framework does not use the EU’s one stop shop system. The feature has been active since 2023 and the investigation started in July 2025. 

The fine of €805 million equates to around 0.47% of Meta’s worldwide revenue. The authority took into consideration the potential impact on around 20 million Android users in Italy, how long the breach had been occurring, a previous ruling in 2019 against Meta and Meta’s lack of cooperation. However, they also took into consideration that Meta had made changes following the complaint. Regulators felt these changes were late and not enough.

US Disrupts North Korean Crypto-Theft Campaign

 

The United States has disrupted FaceStealer, a North Korean cyber campaign that allegedly stole more than $400 million in cryptocurrency through deepfakes, hijacked messaging accounts, and fake technical “fixes.” The operation targeted crypto and Web3 professionals as well as open-source developers, showing how social engineering can be as damaging as a conventional software exploit. 

According to the FBI, attackers hijacked accounts on Telegram, LinkedIn, Slack, and Discord and used them to invite victims to video meetings. During those calls, they displayed recordings of people the targets knew—including people who had already been compromised—to create a convincing sense of trust and urgency. While a victim waited for a meeting to begin, the hackers secretly recorded webcam footage. Those recordings could then be reused in later meetings, sometimes alongside footage of multiple familiar people, making the deception increasingly difficult for the next target to recognize. 

After building trust, the attacker claimed that a technical problem had occurred and displayed a fake error message. The victim was then directed to a link offering a supposed update, installer, or repair—effectively a ClickFix-style lure designed to make running malicious code seem routine. The malware stole cryptocurrency-related data and credentials for video-meeting services such as Zoom, Google Meet, and Microsoft Teams. 

It also exposed victims’ contact lists, social media accounts, communication applications, and webcam videos, giving attackers material to expand the campaign. Researchers attributed FaceStealer to the North Korean-linked BlueNoroff group. The campaign reportedly identified 677 targets across 58 countries, with a strong focus on founders and senior executives in the cryptocurrency and Web3 sectors. 

The attackers sometimes waited months, or even more than a year, before exploiting an initial compromise—likely allowing victims’ cryptocurrency holdings to grow. The FBI also highlighted attempted attacks against maintainers of widely used npm and Rust packages, underscoring the risk to the broader open-source supply chain. 

The U.S. government seized the cloud infrastructure supporting the campaign after it had operated for 18 months. Authorities also identified more than 900 secretly recorded webcam videos of technology workers, illustrating the scale of surveillance and social manipulation involved. In a related action, the U.S. Department of Justice said it froze more than $2.7 billion connected to a $6.4 billion Binance crypto heist, with court authorization to seize or restrain more than $1.2 billion of that amount. These actions show that disruption can involve both infrastructure takedowns and financial countermeasures. 

Users should join meetings only through official applications and invitation codes, independently verify unexpected meeting invitations, and keep webcams off unless they are genuinely needed. Most importantly, they should never run scripts, updates, or “fixes” prompted by an unexpected technical error during a call. FaceStealer demonstrates that cybercriminals no longer need to break through technical defenses first; they can exploit human trust, familiar faces, and urgency. For crypto holders, executives, and developers, verification before action is now a core security control.

Falcon C2 Malware Turns Web Browsers Into Espionage Tools


The Falcon cyberespionage framework, formerly known as XG, targets government systems by exploiting web browsers to exploit sensitive information and maintain covert access to compromised systems. By utilizing malicious JavaScript and deceptive browser extensions, the framework monitors user activity, collects credentials and has access to confidential communications without relying on conventional malware execution. 

It is reported in Palo Alto Networks' Unit 42 report published on November 11, 2026 that Falcon was used between March and May of 2026 in campaigns targeting government entities in one Middle Eastern country and four Southeast Asian countries. Ministry of foreign affairs, defense and interior, police departments, intelligence agencies, military entities, and government email systems were affected by the vulnerability. 

As it operates within the browser environment, the framework is difficult to identify through traditional endpoint security monitoring, which makes its activities more difficult to detect. Instead of using suspicious executable files, attackers inject malicious JavaScript into legitimate web applications and webmail portals in an effort to conceal their activities. 

In the case of a compromised website, the browser retrieves the malicious script from the Falcon command-and-control (C2) infrastructure when the targeted user visits the compromised site. Researchers have observed that the framework generates an implant separately for each browser session. This implant consists of two JavaScript components containing configuration details and functions for communicating and executing commands. 

An XOR operation of a single byte is performed to obfuscate the combined script before delivery, converting its contents into a series of numerical values that are decoded and executed within the browser. A 32-character session identifier, stored locally in the browser, and in cookies, is also used for persistent tracking. In order to blend in with ordinary browser data, the malicious entries employ a naming convention mimicking Baidu Analytics identifiers. 

Falcon extensions are equipped with the capability of storing the identifier within their extension storage when installed. For command-and-control communication, the implant establishes a WebSocket connection to the attacker's server while the compromised webpage is available. In order to maintain the connection, a periodic heartbeat message is sent to maintain the connection and an AES-256-CBC encryption system is used to protect data exchanged with RSA-based key negotiation. 

In addition to the framework's built-in features, the Comet communication method provides a fallback mechanism for executing arbitrary JavaScript commands, transmitting collected information, and managing compromised browser sessions once connected. Through its built-in functions, attackers are able to control infected browsers effectively by exfiltrating data, labeling sessions, and receiving operator notifications via Telegram.

It was also found that Falcon and PeckBirdy, a scripting framework previously described by Trend Micro, share many similarities. In light of the shared URL structures, payload delivery methods, communication protocols and session storage conventions, Unit 42 concluded with high confidence that both frameworks are variants of the same underlying toolset. 

Falcon Extension Expands Surveillance Across Browsers and Internal Systems As part of Falcon's broader control over compromised browsers, the company uses dedicated Chrome and Firefox extensions, which in turn conceal itself as a legitimate PDF viewer called "PDF Viewer" and request 40 permissions. These permissions include access to browser credentials, cookies, browsing histories, downloads, and network activity, among others. 

There is no indication as to how these extensions are installed by the operators, however the management panel appeared to contain tools for silent installation. As soon as the extension is activated, it tracks activity across visited websites and collects information through background processes. It is capable of capturing Gmail, Discord, Zalo chat databases, and X direct messages. 

The system can also monitor clipboard activity as well as intercept web requests containing text or JSON data. Collected information is temporarily stored and sent to the command server. Another noteworthy feature allows attackers to use the victim's browser as a proxy. 

Operators can send requests using session cookies and stored credentials to authenticate a browser session and gain access to internal resources under the victim's name by using stored credentials. Moreover, Falcon is capable of intercepting selected downloads, cancelling the original request, and redirecting the user to an attacker-controlled file while retaining the original filename. These capabilities increase the risk of account hijacking and further malware delivery. Between March and May of 2026, Unit 42 has identified several government-oriented campaigns. 

One Middle Eastern country has been compromised by attackers who inserted malicious scripts into the header of a Ministry of Foreign Affairs Roundcube webmail portal. Researchers have identified 39 Roundcube instances within the country which are affected. A police entity was targeted by attackers who harvested user names through an internal application in a Southeast Asian country. 

After the fake Adobe Flash Player update prompt, selected users received an implant referred to as Antino. As part of a separate attack against a Justice Department-affiliated organization, a malicious Chrome extension remained active for more than three weeks. Operational personnel captured credentials and screenshots of sensitive internal documents during the intrusion. 

By adding a Windows-based capability, Antin adds a new capability to the framework. A Rust-based implant, authored by the researcher, uses Microsoft OneDrive to communicate with the framework, uploading system information, and receiving commands via JSON files. As well as executing shell and PowerShell commands, file transfers, collecting system information, and executing programs, it establishes persistence via the Windows Registry Run key. 

It is recommended that Unit 42 examine unauthorized browser extensions, suspicious script injections in internal web applications, and unusual browser storage entries utilizing the Hm_lvt_ naming convention in order to identify potential infections. Security teams should also investigate unexpected OneDrive activity, particularly repeated JSON file transfers that utilize paths such as antino/heartbeat and antino/antino_upload. 

It is demonstrated that Falcon combines conventional Windows malware capabilities with browser surveillance to provide attackers with multiple methods for maintaining access to government information and gathering sensitive data. As a result of the discovery of Falcon, browser-based espionage frameworks pose increasing threats. 

Through a combination of malicious extensions, JavaScript implants, and Windows-based malware, attackers are able to monitor user activity and access sensitive government information. Several steps can be taken to reduce the risk of similar intrusions, including strengthening browser security, auditing installed extensions, monitoring suspicious script injections, and investigating unusual cloud storage activity.

Attackers Exploit Critical UnrealIRCd Flaw Enabling Server Command Injection

 

A high-severity vulnerability in UnrealIRCd, an open-source IRC server, is being actively exploited by attackers. Tracked as CVE-2026-114713, the flaw has a CVSS score of 8.6 and allows malicious users to inject server-to-server commands that execute with elevated authority. CISA has added it to its Known Exploited Vulnerabilities catalog, making urgent patching essential for affected organizations. 

The vulnerability arises from improper neutralization of delimiters in UnrealIRCd’s labeled-response module. In versions 6.0.0 through 6.2.7.0, the software fails to properly escape the IRCv3 “label” message tag when echoing it in replies. On networks with two or more linked servers, this lets any connected user inject commands into server-to-server communication and potentially perform actions reserved for server or IRC operators. 

The flaw is especially serious because it can undermine the trust between linked IRC servers and enable arbitrary command execution. UnrealIRCd maintainer Bram Matthys described it as the most critical UnrealIRCd vulnerability discovered in the past 15 years. Exploitation reportedly began just one day after the security hotfix was released on November 7, 2026, showing that attackers are moving quickly to target unpatched systems. 

CISA added the vulnerability to its Known Exploited Vulnerabilities catalog after reports of real-world attacks. Under Binding Operational Directive 26-04, federal civilian executive branch agencies must apply the required fixes by November 16, 2026. The short deadline reflects the urgency of the threat, particularly for internet-facing systems or organizations operating multi-server IRC networks. 

Administrators should immediately upgrade UnrealIRCd to version 6.2.7.1 or later, which fixes CVE-2026-114713 and several other vulnerabilities. Those unable to update right away should apply the available spamfilter workaround, review logs for suspicious activity, and ensure every linked server is patched. The incident is a reminder that prompt patching and strong access controls are essential to prevent newly disclosed flaws from becoming active attack vectors.

Trezor Confirms Hardware Implants in Three Safe 5 Wallets Sold Through Malaysian Reseller

 


Trezor has confirmed that three of its Safe 5 hardware wallets contained malicious circuit board implants capable of stealing cryptocurrency recovery phrases and transmitting them over a mobile network to an attacker-controlled server. The company published its investigation findings on November 13 and released a firmware patch two days earlier that neutralizes the implants found so far.

All three affected devices were purchased from CryptoBilis, a Malaysia-based hardware wallet retailer operating across Southeast Asia, between August 20 and September 23, 2026. No customers who bought from other regional resellers have been flagged, and no affected CryptoBilis customer has reported stolen funds so far.


How the Implant Works

The malicious component is a secondary circuit board installed between the Safe 5's main board and its display. It does not touch the legitimate firmware or the wallet's Secure Element, which is precisely what makes it difficult to catch through standard software checks. Instead, it sits passively and watches the screen.

When a user sets up a new wallet or restores an existing one, the implant reads the recovery words as they appear on the display. It can also capture passphrases. Once it has what it needs, it encrypts the data and sends it over a mobile network to a remote server. If the device has no mobile connection at that moment, the implant holds the data and keeps attempting transmission until it goes through.

The design mirrors what security researchers at Tibane Labs found inside tampered Ledger wallets traced to the same reseller weeks earlier. In those devices, the implants used an eSIM and a shielded LTE module alongside a microcontroller, with chip markings scraped off in at least one variant to slow identification.


How Trezor Found Them

The investigation began in October 2026 after a customer reported finding an unfamiliar circuit board inside a Safe 5 purchased from CryptoBilis. At the time, Trezor had not yet received the physical device and could not confirm what the implant was actually doing. It issued a warning and asked CryptoBilis customers to get in touch.

Forty-eight customers responded. Trezor examined some devices directly in its lab and checked others by reviewing photographs of internal components submitted by owners. That process turned up two more compromised wallets beyond the original one.


The Fix and What It Cannot Do

Firmware version 2.13.1, released on November 11, is designed to block the specific implants Trezor has examined from reading information off updated devices. The company described the patch as making "the current batch of implants useless."

There is an important limit to what the update can accomplish. If a device was implanted and a user set it up or restored a wallet before installing the firmware, the recovery phrase was already captured and sent. The patch stops future captures but cannot retrieve data that has already left the device.

Trezor is advising everyone who purchased a Safe 5 from CryptoBilis to move their funds to a new wallet generated with a freshly created recovery phrase. The company is offering replacement devices to any customer who bought from CryptoBilis since March 2026, including those whose devices have not been confirmed compromised.

CryptoBilis sits at the center of a supply chain problem that has now touched two of the most recognized hardware wallet brands. Ledger confirmed implants in its own devices sold through the same reseller in early October, shortly after users began reporting fund losses. Ledger's investigation showed that all reported drains traced back to CryptoBilis, and the company asked the retailer to stop selling and shipping its products.

Tampered Ledger devices were reportedly sold at roughly half the standard retail price, which in hindsight was a signal that something was wrong with how those units were sourced.

Trezor had already announced plans in October to tighten its reseller network following the Ledger reports, before its own implants were confirmed. It has since cut approximately 80 percent of its global reseller partners. The company said the removed resellers were not themselves untrustworthy, but that they did not meet the stricter supply-chain security requirements Trezor put in place after the CryptoBilis situation came to light. Remaining partners now face tighter controls over how devices are sourced, stored, and physically handled before they reach customers.


What Buyers Should Do

Anyone who purchased a Trezor wallet from CryptoBilis is being directed to contact Trezor directly. Those who set up or restored a wallet on the device before the November 11 firmware update should treat their current recovery phrase as exposed and generate a new one on a trusted device. Trezor's recommendation is to move funds before doing anything else.



UK Data Protection Regulator Sees Unprecedented Rise in Cyber Incident Reports


There was a record number of cyber incidents reported by British organizations to the country's data protection regulator during the third quarter of 2026, demonstrating the increasing strain on the UK's cybersecurity landscape. The latest data from the Information Commissioner's Office (ICO), which has been analyzed by Recorded Future News, indicates that 1,371 cyber incidents were reported from July to September, surpassing the previous quarterly record set in 2023. It is also estimated that the UK will surpass its previous record for cyber incident reports, which was also set in 2023. 

In addition to cyber-related incidents, the regulator received 4,604 reports regarding data security incidents during the third quarter, marking the highest quarterly total ever recorded. These included non-cybersecurity incidents, for example, sending sensitive emails to the wrong recipients accidentally. 

There are growing concerns among cybersecurity firms about the increasing number of British organizations appearing on data leak sites operated by cybercriminal groups. These groups increasingly use stolen information to pressure their victims into paying extortion demands. In addition, incident response providers have reported a sharp increase in demand, with employees at some firms stating that they have had to turn away prospective clients as a result of capacity limitations. 

ICO figures, however, provide a mixed picture of the ransomware threat. While reports of extortion-related activity continue to increase across the industry, the number of ransomware incidents formally reported to the regulator has continued to decrease. In 2023, the ICO recorded 1,253 ransomware incidents, followed by 752 in 2024 and 620 in 2025. It is estimated that 321, including 102 cases in the third quarter, have been reported in the third quarter of 2026, compared to 111 cases reported in the second quarter of 2026. 

ICO reports of cyber incidents are generally classified as 'other cyber incidents' rather than specifically classified as ransomware, phishing, or malware, which are most frequently reported. It is difficult to compare ransomware figures directly since the regulator's classification does not clearly indicate whether data theft and extortion without file encryption are included. While these limitations have been acknowledged, cybersecurity researchers have identified a significant increase in organizations being publicly identified by ransomware groups.

Rafe Pilling, director of threat intelligence at Sophos, stated leak-site numbers are imperfect but indicate a rise in ransomware attacks and data theft extortion activity, especially in the UK. As reported incidents increased, they were not limited to a particular industry. Retail and manufacturing organizations recorded the highest number of incidents, with reports increasing from 205 in the second quarter to 296 in the third quarter. 

A substantial increase has also been observed among charitable and voluntary organizations, with incidents rising from 79 to 145 during the same period. A significant increase has been observed at online technology and telecommunications companies, where incidents have increased from 76 to 120. There was a decline in reports in education and childcare among the six most affected industries, which fell from 135 to 115 reports.

Although there have been an increasing number of complaints, only a small percentage have resulted in formal regulatory investigations. ICO officials confirmed that only 18 of 1,371 cyber incidents reported during the third quarter were investigated, while the majority were handled by informal regulation or were closed without a formal investigation being initiated. 

Moreover, artificial intelligence is gaining traction in the evolving cyber threat landscape Rafe Pilling of Sophos cites the growing use of artificial intelligence by established cybercriminals and attacks involving AI agent frameworks as contributing factors to the wider threat. It is possible for threat actors to increase the speed and scale of their operations through the use of these technologies, facilitating the identification of vulnerabilities and the implementation of attacks. 

In the healthcare sector, the wider impact of unauthorized data access has also been of concern. ICO received and assessed more than 300 reports of unauthorized access to patient records between January and October 2026. Healthcare employees are reported to have accessed medical records without a legitimate reason, viewed information belonging to individuals they are acquainted with, and shared confidential patient information. 

Health care leaders have been instructed by the regulator to improve access controls, monitor suspicious activity, and take appropriate action against employees who have accessed records without authorization. Although established defensive measures remain essential for reducing cyberattack exposure, security experts continue to emphasize how effective these measures remain. 

To prevent unauthorized access to internet-facing systems, Pilling recommended that vulnerabilities in these systems be addressed and multifactor authentication, as well as passkeys, be implemented. Several organizations across all sectors are vulnerable to cyberattacks. The Information Commissioner has stressed how important it is to protect personal information from cyberattacks.

A strong cyber resilience program is essential, according to Jonathan Ellison, director of national resilience at the National Cyber Security Centre, who pointed out that many successful attacks continue to exploit known security vulnerabilities. In addition, artificial intelligence is facilitating the identification of vulnerabilities and potential exploitation of those vulnerabilities at a faster rate. 

Despite the growing trend of cybercriminal activity, British organizations have been under increasing pressure to improve their security controls, detect incidents and protect sensitive information as a result of increasing cybercriminal activity. These record figures underscore the increasing pressure that UK organizations face when it comes to strengthening their cybersecurity practices and protecting sensitive data. 

s criminal groups increasingly rely on data theft and extortion, effective access controls, timely security updates and phishing-resistant authentication remain essential. Organizations must also improve incident monitoring and response capabilities to limit exposure and maintain public trust.

Ransomware Attack Disrupts Belarusian Cloud Provider ActiveCloud, Affecting Business Services

 

A ransomware attack on Belarus-based cloud services provider ActiveCloud has caused issues with websites, business email and virtual servers. The company has confirmed that their systems have been breached and some areas have been locked by ransomware. 

The company said on Tuesday that they had been hit by the ransomware attack which has affected their cloud hosting, email and customer support. Whilst some critical elements of their infrastructure have been restored by Wednesday, it will take longer to get customer systems back up and running. ActiveCloud said on Friday that they have now restored their core services, however some customers are still having issues. 

They added that their technical teams have been working around the clock to get everything back up and running and the most difficult part of the recovery process is now complete. The ransomware attack has impacted a number of services including their core cloud hosting product E-Cloud, secure hosting E-Cloud Protected and their business email SmartMail. Some customers also had issues getting their virtual machines running. 

ActiveCloud said that during their investigation they have found no evidence that customer data has been compromised. They have not said how the attackers gained access to their systems. The ransomware attack has impacted organisations using ActiveCloud. Belarus news organisation Smartpress have confirmed that they use ActiveCloud to host their website, however they are still publishing. Domino’s Pizza website and mobile app in Belarus have also had some downtime due to the issues. 

ActiveCloud provide cloud hosting, virtual servers, business email and other IT services to businesses and organisations in Belarus and Russia. This means that when issues occur with these services, a number of customers can be impacted. The attack comes after a number of incidents targeting hosting companies in Belarus and neighbouring Russia. On November 8, Russian hosting provider ESTT were hit by a ransomware attack which impacted their cloud services. This caused issues with websites, virtual servers and other customer services. 

They said that whilst their cloud management systems had been targeted, there was no evidence that customer data had been compromised. Just days earlier another Russian provider Beget fell victim to a destructive cyber attack. Attackers reportedly gained access to their infrastructure management systems and ran scripts to wipe data from some areas of their cloud. 

This caused issues with websites and online services for businesses, media and government. They also said that some of their virtual servers had been lost meaning it was harder to get everything back up and running. There is no confirmed evidence linking the attacks on ActiveCloud, ESTT and Beget. None of the companies have identified who is responsible.

Cyberattack on Quantum Systems Disrupts German Military Drone Operations


German defence technology company Quantum Systems has confirmed that it was targeted in a cyberattack in late October.

The incident involved a compromised software update server used to distribute updates for the company's QBase ground-control and mission-planning software.

The company said it detected suspicious activity linked to an active cyberattack carried out by unidentified hostile actors. It responded by working with government authorities to contain the threat and ensure its unmanned systems could safely resume operations.

Quantum Systems manufactures reconnaissance and interceptor drones, along with software used to control and manage their missions. Its drone systems are deployed by the German military and are also used in support of Ukraine.

Malicious software update compromises drone systems

According to reports by German newspaper Der Spiegel and the Financial Times, attackers compromised a server responsible for distributing software updates for Quantum Systems' QBase platform.

The attackers placed a malicious update file on the compromised server, disguising it as a legitimate software update. Since QBase is used for ground control and mission planning, the incident raised concerns that malicious software could reach systems used by military drone operators.

Der Spiegel reported that the Vector reconnaissance drone, known as Falke in German military service, is among the systems whose missions are planned using QBase software.

The unauthorised update triggered alarms within Quantum Systems after it was distributed to customers. However, it remains unclear how many customers downloaded or installed the malicious file.

German military grounds drones as precaution

The cyberattack disrupted German military drone operations, prompting the armed forces to ground Quantum Systems' drones as a precautionary measure.

According to media reports, the decision also resulted in the company's drone systems being excluded from a recent military exercise.

Quantum Systems said it believes the company was targeted because of its support for Ukraine. The company has also highlighted the growing number of cyberattacks against European defence organisations.

German authorities investigate the incident

Germany's military counterintelligence service (MAD), domestic intelligence agency (BfV), and Federal Office for Information Security (BSI) are involved in the investigation.

Quantum Systems said it is cooperating with government authorities to investigate the incident and address the security concerns. However, the company has not publicly identified the attackers or provided details about their methods and objectives.

In July, Australian drone manufacturer CubePilot also experienced a DNS hijacking attack that caused operational disruption.

Hackers Exploit New N-able N-central Zero-Day Hours After PoC Release

 

Hackers began exploiting a new zero-day vulnerability in N-able N-central within hours of a proof-of-concept exploit becoming public. The flaw, called 4EverAble2Shell, can let unauthenticated attackers execute code with root privileges on vulnerable N-central servers, including systems running the latest available patches. 

The vulnerability was published on GitHub by security researcher Sean Bales, two days after N-able released fixes for several other flaws he had disclosed. 4EverAble2Shell chains an exploit for a recent Apache Axis vulnerability, CVE-2026-90436, with an unspecified flaw affecting N-central deployments that have the Legacy API enabled. The Apache Axis issue has a CVSS score of 9.8, reflecting its critical severity. 

Modus operandi 

The attack chain first exploits the Apache Axis bug to achieve remote code execution. It then attempts to elevate its privileges to root and run a shell script. Researchers said the chain works against N-central servers updated to 2026.4 HF2, build 2026.4.1.26, which had already received fixes for earlier Able2Shell zero-days. This means applying the latest hotfix alone does not fully eliminate the risk. 

N-able responded by restricting several N-central features and integrations, including the Legacy API and Intune integration. The company said it had identified additional indicators of compromise and was working with affected customers to assess and mitigate potential risks. On November 12, Bales also published proof-of-concept code for Agent2Shell, a set of roughly a dozen zero-day flaws that could allow attackers to execute commands on managed Windows agents with System privileges. 

Threat intelligence firm Previdian reported that attackers began using the 4EverAble2Shell proof of concept within hours of publication. WatchTowr also observed probes targeting N-central systems with the Legacy API enabled. Lupovis and Huntback found evidence of successful compromises about five hours after the exploit was released, with attackers deploying an XMRig cryptocurrency miner and using systemd or cron for persistence. 

The attackers named each miner after the victim’s IP address. Lupovis said the attacker’s wallet showed 21 rigs connected to compromised N-central servers in the United States, South Africa, Canada, the United Kingdom, Germany, France, and Sweden. The researchers said their decoy systems did not execute the exploit, confirming that the listed systems were real victims. 

Huntback found that 19 victims had already applied N-able’s latest patches. The firm warned that the miner may be the only observed payload, but the privilege escalation gives attackers root access to a server that manages customer endpoints. Security teams should therefore treat any successful exploitation as a full compromise rather than a minor cleanup task. 

Organisations using N-central should immediately disable the Legacy API where possible, apply vendor guidance, review logs for exploitation indicators, and rotate credentials connected to affected systems. They should also inspect AWS, Azure, and other connected environments for suspicious access, because root-level compromise of an RMM server can expose downstream customer networks.

PostgreSQL’s Largest Ever Security Release Patches 52 Flaws, Including a 22-Year-Old Bug Any Logged-In User Could Weaponize

 


The PostgreSQL Global Development Group shipped security updates on November 12 for all five supported major versions, issuing fixes for 52 vulnerabilities at once: the largest security release the project has published. Thirty-two of the 52 flaws carry a CVSS 3.1 score of 8.8, with no user interaction required, full confidentiality and availability impact, and network reachability through a low-privilege login. The fixed releases are 18.7, 17.12, 16.16, 15.20, and 14.25.

At the center of the batch is CVE-2026-6460, a type confusion flaw in how PostgreSQL handles composite types — data structures built from named fields. When a field's type is changed after values of the original type are already stored, PostgreSQL's binary representation keeps those old bytes intact while the catalog metadata shifts around them. The server then reads a stale value through the new type's output function. That mismatch is enough for a database user who can create objects to run arbitrary code as the OS account running PostgreSQL, no superuser status, no extensions, no file access.

The trigger takes exactly four SQL statements. A user creates a composite type, prepares a query using it, alters the attribute to a different type, then executes the prepared query. The backend selects the wrong output handler, dereferences a null pointer, and crashes. That crash is the entry point.

Security researcher Mehmet Ince found the flaw and published a writeup alongside a demonstration on PostgreSQL 18.6. He traces the root cause to a commit made May 5, 2004, the one that added ALTER TABLE ... ALTER COLUMN ... TYPE. That logic never accounted for prepared statements holding values built against the old type. The code sat there for 22 years. His exploit chain defeats ASLR through a related confusion involving PostgreSQL's unnest() function, then calls system() through a forged object whose methods table points at the system call. He stopped short of publishing that final step. He found 21 variants of the problem in total, and six of the 52 CVEs in this release trace to his work. The release credits 18 researchers for CVE-2026-6460 alone, including PostgreSQL core developers Heikki Linnakangas and Andres Freund, along with the OpenAI Security Research Team and the Anthropic OSS program.

Before going public, Ince spent August coordinating with every major managed provider. He shared working proofs of concept with AWS covering both Aurora and RDS, Microsoft for Azure Database for PostgreSQL, Google for AlloyDB, Supabase, Databricks, and Ubicloud. Google AlloyDB escalated the report to its highest internal priority. Databricks validated the exploits the same day they arrived. Several vendors deployed their own mitigations before the upstream release shipped. Their current patch status is not public, so administrators on managed services should verify the minor version their provider is running.

The release also contains a flaw that skips authentication entirely. CVE-2026-116322, rated 5.3, lets any client restart a PostgreSQL 18 server without logging in. It involves a cancel request and a spinlock held during the authentication timeout window. Two further vulnerabilities sit in the client tools: a crafted archive fed to pg_restore can execute code as whoever invoked it, and a compromised source server can inject commands through the restore script inside pg_dump's tar output to any psql client connecting to it.

The November release permanently closes the PostgreSQL 14 branch. Version 14.25 is its last update. Administrators still on that version are running unsupported software from today. PostgreSQL 15 reaches the same status in November 2027.

Upgrading involves more than swapping binaries. The fix for CVE-2026-6460 changes the server's internal ABI for C-language extensions, which must be rebuilt against the patched version. Extensions compiled for the new release will not load on an unpatched server, so the upgrade and the rebuild must happen together. A new server setting, composite_type_mismatch, enables the type-version checks behind the fix; the project says disabling it carries security risk. Client tools must be updated on every machine running them, not just servers. Clusters managed by Patroni or any custom service unit need a manual restart. Users of incremental backups should take a new full backup before anchoring further incrementals. No workaround exists for the principal vulnerability on servers that cannot be patched, and PostgreSQL has reported no attacks in the wild.

The same acknowledgment list that names Ince, Linnakangas, and Freund also includes AI-assisted tooling. That dynamic cuts both ways. PostgreSQL 19, normally shipped in September or October, was pushed to November 19 partly because AI and LLM tools generated enough new reports to overwhelm the maintainers' review capacity before the feature freeze. Developer Robert Haas noted that LLM-drafted patches still need human review to meet project standards, and consultant Christophe Pettus pointed to the volume of low-quality machine-generated reports as a growing burden. The same tools that surfaced a 22-year-old bug made it harder to ship the next version.


SilentAir Hacks Asian Telecom Networks to Intercept Calls and SMS Verification Codes

 

A cyber espionage group known as SilentAir has been attacking telecoms infrastructure throughout Asia to listen in on selected individuals’ calls and text messages. This was uncovered by Enea, a telecom security firm based in Stockholm. They believe with high confidence that the campaign is state-sponsored, however it is uncertain how connected it is to China. Enea were able to trace the attacks to compromised devices within mobile operators in at least 6 countries throughout Asia. 

They have informed the operators but cannot confirm that all devices are now clean. SilentAir attacked the trust between mobile networks using the SS7 and Diameter protocols to communicate. This communication occurs on the IPX network which links all operators together. They sent false UpdateLocation messages to the compromised devices claiming they were the serving network for targeted users. When this was accepted calls and texts were redirected towards the attacker. Whilst they were intercepting some calls, Enea were able to see SMS 2FA codes being captured straight after the redirection. This suggests they were trying to breach other accounts for their victims. 

However during their investigation there was no confirmation that they were able to take over any accounts, nor was there any evidence of voice calls being intercepted. Intercepting calls made up 18.3% of the attacks they observed compared to only 2.1% from their previous research into common signalling attacks. There were many high value targets such as political and government individuals. 

In some cases multiple compromised devices were used across different countries to target the same individuals suggesting there was some central control. The attacks occurred in short bursts. At times thousands of subscribers were targeted but then nothing happened for months. Whilst the main focus was Taiwan, networks across Southeast Asia, East Asia, East Africa, Central Asia, Middle East and Europe were also targeted. 

There was a large amount of silent SMS being used. Many targeted Taiwanese subscribers during the evening, potentially to check if the redirection was working. Many were sent during the day to subscribers on other networks. The messages had generic English text relating to promotions and motivation, so could have been seen as spam if the silent settings were turned off by the operators. Enea started to see strange signalling activity in early 2025. 

Eventually they were able to see compromised devices sending and receiving attack commands confirming that the operators internal infrastructure had been compromised. They looked into potential links with another telecom focussed threat group called Liminal Panda but there wasn’t enough evidence to connect them. SilentAir also had similarities to SCTPE, a Linux based tool used to manage SS7 and Diameter traffic. This has been referred to as SIGweaver within a government advisory from Singapore. 

However the capabilities differ and there was not enough operational security to link them. Liminal Panda activity was also detected by Enea across multiple customer networks in early 2026. They blocked GTPDoor backdoor traffic across at least 5-10 operators. The new version of this is harder to detect as it hides the commands within GTP-U traffic.

Enea recommend using GTP-C and GTP-U firewalls, treating all IPX connections as untrusted and ensuring telecom monitoring is brought into the wider IT security.

Operation Endgame Takes Down Three Malware Networks, Recovers 6.4 Million Stolen Logins


An international law enforcement operation has shut down the infrastructure behind three major malware operations: Gootloader, CastleRAT and StealC, seizing 235 servers and 257 domains used by cybercriminals to distribute malicious software, steal sensitive information and support ransomware attacks.

Operation endgame disrupts three major malware networks

The coordinated action, conducted as part of Operation Endgame, also resulted in the identification and seizure of approximately 6.4 million stolen login credentials belonging to victims worldwide. According to Germany's Federal Criminal Police Office (BKA), the credentials were associated with more than 40,000 victims.

Gootloader spread malware through compromised websites

Gootloader is a malware loader that enables attackers to gain initial access to compromised computers and subsequently install additional malicious programs, including ransomware. Its operators distributed malware through fake legal documents hosted on compromised websites, frequently exploiting hacked WordPress sites.

The attackers also used search engine optimisation (SEO) poisoning to manipulate search results and direct unsuspecting users towards malicious downloads. 

Since 2018, Gootloader has infected at least 25,000 computers worldwide, according to the U.S. Department of Justice. In the United States alone, the malware has been linked to ransomware attacks against at least 44 victims, resulting in estimated losses of approximately $28.8 million.

As part of the operation, authorities dismantled 14 servers and 218 domains associated with Gootloader and cleaned 681 compromised websites.

Castlerat and stealc enabled remote access and credential theft

The investigation also targeted CastleRAT, a remote access trojan that allows attackers to remotely control infected systems and use them for malicious activities. Authorities seized 120 servers and 39 domains linked to the operation.

Meanwhile, StealC, an information-stealing malware, was another major target. The malware is designed to extract sensitive information, including passwords, stored credentials and digital identities, from compromised computers. 

This latest disruption follows an earlier law enforcement action against StealC in June 2026. Following that operation, its operators reportedly rebuilt their infrastructure and resumed activities to evade investigators.

Europol's European Cybercrime Centre (EC3) supported the investigation through cyber intelligence, financial tracking and victim identification. Authorities also plan to make information about affected users available through several cybersecurity platforms, including Have I Been Pwned, and the Shadowserver Foundation.

Although no arrests were announced during this latest action, Dutch authorities have continued investigations targeting Gootloader's suspected main operator.

Hackers Steal Personal Information in Cyberattack on University of Texas at Arlington


UTA has confirmed that hackers have stolen personal information as a result of a cyberattack last month that affected its IT environment. A university investigation into unauthorized activity has led to this disclosure, although the university has not yet determined the full extent of the data exposure or identified all individuals whose information may have been compromised as a consequence of the data exposure. 

During a response to Recorded Future News, a university spokesperson confirmed the investigation identified data theft, but did not provide specific details regarding which types of information were accessed by the attackers. As part of the university's ongoing efforts to determine the scope and nature of the compromised data and identify potentially affected students and employees, we are currently conducting research. 

According to UTA, individuals who are identified as affected will receive notifications describing the incident, the information involved, and the methods available for protecting their personal information. In addition, the university plans to provide support and guidance to individuals whose information has been exposed. 

In the initial phase, the incident was noticed following disruptions involving MachForms, an online platform used for registrations, service requests, surveys, and other administrative functions. UTA immediately took the platform offline as a precautionary measure following the discovery of the security incident. 

While the investigation continues, MachForms will remain unavailable. The university has also monitored its IT environment to detect any further impacts on its systems or daily operations. There has been no specific timeline provided for the restoration of the affected service. With approximately 41,000 undergraduate and graduate students, The University of Texas at Arlington is one of the most prestigious higher education institutions in Texas. 

It is alarming to learn that personal information belonging to academic and administrative members of the university was stolen, raising concerns about the possibility of sensitive data being exposed. A ransomware attack was claimed earlier this week by the Qilin ransomware group. Qilin has established itself as one of the most active ransomware groups targeting a variety of industries. 

Halcyon Ransomware Research Center figures indicate that between July and September 2026, the group is believed to be linked to 344 alleged ransomware incidents, placing it among the top ransomware operators at that time. In addition to the recent arrest of one of the ransomware operation's prominent affiliates in Japan and extradition to Germany, Qilin has also been attracting attention as a result of a series of developments involving its affiliates and leadership. 

The Russian national Aleksey Mikhailovich Yakovtsev has been identified as a leader of the ransomware network by cybersecurity companies and independent researchers, adding to ongoing investigations into the individuals behind the ransomware network. In addition to claiming responsibility for attacks on the US Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF), the group has also claimed responsibility for attacks on government and institutional targets in the past few months. 

Using its double-extortion strategy, the organization threatens to publish the stolen files if victims refuse to pay ransom. These tactics increase the workload on organizations, particularly those that handle large volumes of personal and administrative information. This incident occurs during a period when higher education institutions are experiencing a series of ransomware attacks. 

According to York University's recent announcement, attackers have accessed and taken substantial amounts of student information, including more than a decade of student records. Besides raising concerns about the long-term exposure of personal information maintained by academic institutions, Vanderbilt University has also suffered from a separate ransomware attack which has adversely affected its operations. 

University officials have advised that it may take several weeks to restore normal operation across the university's systems. The university's efforts to recover are concentrating on essential services such as payroll, payment processing, admissions, course registration, and public safety. Vanderbilt remains under investigation for possible data theft. 

A group responsible for BYOD ransomware has claimed responsibility for the incident at Vanderbilt, as well as recent attacks that affected Michigan State University and New Mexico University. Newly emerging groups and their operations are relatively unknown to researchers. There has been an increasing number of attacks against universities, which have highlighted the risk faced by educational institutions that maintain extensive student, employee, and administrative databases. 

Having disruptions to academic services, combined with unauthorized access to personal data, can adversely affect institutions and their communities for a long period of time. Immediately, the top priority at UTA is determining the scope of the breach, identifying those affected, and restoring the impacted services in a secure manner. 

As higher education institutions manage large quantities of sensitive student and employee data, cybersecurity risks are becoming increasingly important. As UTA continues to assess the extent of the breach and identify affected individuals, this case illustrates the importance of strengthened data protection measures, timely incident response, and continuous monitoring of university information technology systems. 

As well as reflecting the persistent threat that ransomware groups pose to educational institutions, Qilin's involvement also demonstrates the possibility of long-term consequences when disrupting operations and revealing data.

Baker Tilly Discloses Third-Party Data Breach Affecting Nearly 196,000 Individuals

 



Baker Tilly Advisory Group has begun notifying clients about a data breach involving an external service provider, after an unauthorized actor obtained personal information belonging to certain clients and their dependents.

The compromised information was stored on a platform operated by a third-party provider that Baker Tilly uses to deliver its client services. According to the company's notification letter, Baker Tilly discovered the incident on September 6, 2026, and completed its review of the affected records on October 28, identifying the individuals whose information had been exposed.

In its notification, Baker Tilly stated that it became aware of a potential cybersecurity incident involving information maintained on the third-party platform. The company subsequently confirmed that an unauthorized party had obtained data associated with some of its clients.


Nearly 196,000 Individuals Reportedly Affected

Although Baker Tilly's notification does not disclose an overall number of affected individuals or identify the third-party service provider, regulatory disclosures provide further details about the incident's scale.

A filing submitted to the Texas Attorney General's Office lists 10,456 affected Texas residents. The disclosure identifies individuals' full names, addresses, Social Security numbers (SSNs), and other information among the compromised data categories.

The same filing reportedly records a nationwide impact of 195,512 individuals. Additional state disclosures include 1,359 affected residents in South Carolina and 2,689 in Massachusetts. However, the company has not independently provided a consolidated figure in its customer notification.

The sample notification letter published through state regulatory disclosures also contains an unfilled placeholder where the specific categories of compromised personal information should appear. Consequently, the Texas filing currently provides the clearest publicly available breakdown of the exposed information.


Baker Tilly Investigates Third-Party Security Incident

Following the discovery, Baker Tilly says it initiated containment measures and engaged external cybersecurity specialists to investigate the incident, establish its scope, and determine which information had been accessed. The company also notified law enforcement authorities and stated that it is cooperating with their investigation.

Baker Tilly maintains that its investigation has found no evidence of continued unauthorized access to its own network or systems. It has also reported no known instances of identity theft or fraud connected to the compromised information.

However, the absence of reported fraudulent activity does not establish that the exposed information cannot be misused in the future, particularly where government identification numbers and residential information are involved.


Affected Individuals Offered 24 Months of Experian Protection

To address potential consequences of the exposure, Baker Tilly is providing affected individuals with complimentary access to Experian IdentityWorks for 24 months.

According to the notification letter, the package includes credit monitoring, identity restoration assistance, and access to specialists who can help investigate and resolve identity theft incidents. The membership also includes up to $1 million in identity theft insurance, subject to the applicable policy conditions and exclusions.

The company has advised recipients to monitor their financial statements and credit reports for unfamiliar transactions or other suspicious activity.


Baker Tilly's Global Operations

Baker Tilly provides accounting, auditing, tax, consulting, and business advisory services. Its international network reported annual revenue of $6.8 billion for the financial year ending December 31, 2025, representing a 21.3% increase over the previous year.

According to its January 2026 financial announcement, the network comprises more than 50,400 professionals operating across 147 territories and 754 offices.

The company has not publicly identified the compromised service provider or explained how the unauthorized actor gained access to its platform. BleepingComputer also reported that it had contacted Baker Tilly seeking clarification about the incident, affected customer numbers, and compromised information but had not received a response at publication time.

No ransomware group had publicly claimed responsibility for the incident at the time of reporting.

Massive GitHub Supply-Chain Attack Exposes Secrets in 1,800+ Repositories

 

A large-scale software supply-chain attack has compromised thousands of GitHub accounts and exposed secrets across more than 1,800 repositories. According to Aikido Security, an attacker used stolen credentials to gain write access to GitHub accounts and planted a malicious continuous-integration (CI) workflow designed to steal cloud credentials, tokens, and other sensitive information. The malicious code was inserted into repositories and often removed within minutes, making the incident difficult to detect. The campaign demonstrates how compromised developer accounts can be weaponized to attack the software supply chain, potentially affecting organizations far beyond the initially targeted repositories. 

The attackers reportedly gained control of 4,837 hijacked GitHub accounts and used their write permissions to insert a secret-stealing payload into repositories. The malicious workflow ran in at least 1,806 repositories, meaning credentials and cloud roles accessible to those repositories’ CI pipelines should be treated as compromised. The campaign began with seemingly harmless pull requests titled “docs: dependency audit notes,” submitted from branches named wfx-docs. These requests were opened in 61,764 repositories, apparently to test whether the compromised accounts could write to them, before malicious commits were added to a smaller group of targets. 

A separate analysis by SafeDep identified 8,093 public repositories that received malicious commits between 12:46 UTC on Tuesday and 04:36 UTC the following day. Because the researchers examined only default branches of public repositories, the actual number of affected repositories is likely higher. In 7,309 repositories, the attacker added the stealer to an existing GitHub Actions workflow. In another 771 repositories, it was inserted as an npm postinstall hook, which could execute on a developer’s machine when they ran npm install. After deploying the payload, the attacker frequently reverted the changes within minutes and deleted workflow logs, sometimes removing the workflow run entirely. 

The malware collected a broad range of sensitive material from CI runners, including GitHub Actions secrets and variables, the workflow’s GITHUB_TOKEN, OIDC and runtime tokens, AI-service keys, and credentials stored in process memory. It also searched for credential files associated with AWS, Azure, Google Cloud, Kubernetes, npm, PyPI, and SSH. The attack was not limited to stealing short-lived tokens: researchers found that the malware could exchange GitHub OIDC tokens for AWS, Google Cloud, and Azure sessions, potentially allowing the attacker to move deeper into cloud environments.

On AWS, the stealer could create long-lived access keys for IAM users and rewrite a role’s trust policy to make it accessible from other AWS accounts. In Azure, it could add federated identity credentials prefixed with wfx-ci- to Entra ID applications, allowing workflows to authenticate even after original tokens were rotated. Repository owners should search for suspicious branches such as wfx-docs, ci-check-[0-9]{4}, and short-lived chore/ branches. They should also look for pull requests titled “docs: dependency audit notes” and commits labeled ci: refresh build cache, chore: add ci helper, ci: restore, or ci: cleanup. 

Other indicators include unexpected workflow files, a .ci-xxxxxx.sh script, an npm postinstall hook, and the SHA-256 hash 89695abb392d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cf. Affected repository owners should immediately revoke the compromised account’s tokens, OAuth grants, SSH keys, and active sessions, then enable two-factor authentication. They must also rotate every secret, variable, cloud credential, and API key that the affected repository or CI workflow could access. Developers who ran npm install on an affected commit should treat their machines as compromised and rotate local keys and credentials. 

Organizations should also review GitHub Actions permissions, restrict workflow access to secrets, require approval for changes from outside collaborators, and monitor cloud logs for suspicious identity activity. This incident highlights that developer accounts, CI systems, and cloud identities are now primary targets in software supply-chain attacks, making strong authentication, least-privilege access, secret rotation, and continuous monitoring essential defenses.

Apache HTTP/2 Security Flaw Exposes Servers to Critical Remote Code Execution Attacks

 

A new vulnerability in Apache HTTP Server could allow an attacker to run malicious code remotely on vulnerable systems. The vulnerability, tracked as CVE-2026-119618, affects the HTTP/2 module (mod_http2) and has a CVSS score of 9.8 which means it is critical. This has been fixed in Apache version 2.4.71 which was released on the 11th November 2026. 

The Apache versions affected are between 2.4.55 and 2.4.70. However, only systems where HTTP/2 has been enabled are vulnerable. Red Hat state "An attacker with network access to a vulnerable system could exploit this vulnerability to take control of the server process." As no authentication is required systems that are network accessible could be at high risk. Red Hat’s analysis of the vulnerability states that there is public research showing a reliable exploit for a server running the default configuration and mod_http2 enabled. The research was not detailed or sourced. 

However, cybersecurity firm Wiz state that there is no exploit available and no attacks have been observed in the wild. HTTP/2 is not enabled by default. It can be enabled globally for all virtual hosts or just on specific virtual hosts. This is done by adding ‘h2’ to the Protocols directive for secure HTTP/2 (TLS) or ‘h2c’ for insecure HTTP/2 (TCP). All configuration files should be reviewed by the security team. Apache recommend upgrading to version 2.4.71. This also includes a fix for a crash issue in mod_md (Important) and a memory overwrite vulnerability in mod_vhost_alias (Low severity). If you are using official builds of Apache then administrators should upgrade to the latest version. This also affects standalone versions of the HTTP/2 module (mod_h2). 

These versions affected are between 2.0.8 to 2.0.42. There is no fixed version available. The GitHub repository has been archived and the latest version published is 2.0.42. The patch is available for some OSs. Red Hat have patched Enterprise Linux versions 9 and 10. However, this vulnerability is rated as Important. This is because the HTTP/2 streams use separate memory allocators making it harder to exploit. Enterprise Linux 8 and below are unaffected. Debian have patched this in their unstable version. Bookworm, trixie and forky are still affected. 
Amazon Linux 2, 2023 and 2027 Preview are waiting on patches. Ubuntu do not have a specific vulnerability page.  
If you cannot patch your systems then Wiz recommend disabling HTTP/2 by removing ‘h2’ and ‘h2c’ from the Protocols directive. This will leave you with HTTP/1.1. This vulnerability was first reported by Anthropic’s OSS Scanner on the 26th October. The scanner uses Anthropic’s AI models to scan open source software. It was also reported by Anthony Weems and Simon Scannell from Google Cloud Vulnerability Research last week. This comes after another vulnerability in Apache’s HTTP/2 module (CVE-2026-23918) was patched in version 2.4.67 in May. Upgrading to this version or any version after up to 2.4.70 won’t protect your systems from this new vulnerability.