Tuesday, November 10, 2026

Git Patches Flaw That Lets Malicious Repositories Execute Code During Recursive Clones

A flaw in Git can let a malicious repository run an attacker's code on a computer that clones it recursively, together with its submodules. The Git project fixed it this week in Git 2.56.1, with matching fixes for the 2.50 through 2.55 series in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1 and 2.55.1.

The flaw, tracked as CVE-2026-111760, is an integer truncation in how Git handles its index. An extremely long path in a repository can pass Git's safety check, but Git then writes it to disk under a shorter name that an attacker can set to .git.

This lets an attacker replace a submodule's .git file with a symbolic link to a folder holding malicious hooks or configuration. Hooks are programs Git runs at set points, so once Git uses that folder, the attacker's code can run.

Submodules matter here because Git refuses to replace a .git folder with a symbolic link, but in a freshly cloned submodule, .git is a file.

The fixed versions, listed in the Git project's release announcement, refuse such extremely long paths before their length can be cut short.

GitHub, which ships Git in its own tools, explained the fixes in a detailed write-up. It advises installing a fixed version from your operating system or Git distributor, and updating any app that ships its own copy of Git.

The company has already applied the fixes to github.com and GitHub Enterprise Cloud. For GitHub Enterprise Server, they are in versions 3.19.15, 3.20.11, 3.21.9 and 3.22.4.

Fixed versions of GitHub Desktop and the GitHub Copilot app are being prepared. GitHub Codespaces and GitHub Actions will also get the fixed Git.

Git for Windows had not released a version based on Git 2.56.1 as of Tuesday at 19:09 UTC, a check of its release tags by The Hacker News found.

Until a fixed version is installed, GitHub suggests these steps, which do not replace the fixes:

  • Clone only from servers you trust.
  • Do not recursively clone repositories you do not trust.
  • Do not merge content or tags you do not trust.
  • Do not process binary patches or fast-import streams from sources you do not trust.

The Git releases also fix five other flaws:

  • CVE-2026-113408: When someone clones an empty repository over Git protocol v2, a malicious server can send a branch name that contains path traversal. With the files reference backend, a later update to that branch can then write outside Git's reference folder.
  • CVE-2026-114467: Merging a tag that carries more than two GPG signatures corrupts Git's stack memory and can cause a denial of service. Hosting services that run such merges for users may also be affected.
  • CVE-2026-114469: A binary patch that expands to a very large size can get past Git's patch size limit of about 1 GiB and crash Git with an out-of-bounds read.
  • CVE-2026-105437: A very large merge, with many conflicts and a large conflict-marker-size attribute, can make Git write past the end of a buffer that is too small, corrupting heap memory.
  • CVE-2026-114466: Three git fast-import features, rewrite-submodules-from, rewrite-submodules-to and export-pack-edges, could be used to read arbitrary files or to create files and add data to them. Git now rejects them in an input stream unless --allow-unsafe-features is set.

GitLab, which assigned CVE-2026-105437, said code-hosting servers are most likely to be targeted through git merge-tree. A server may run that command to check whether a pull or merge request can be merged.

The conflict-marker-size attribute can be set in a .gitattributes file committed to a repository. If a server reads attributes from the repository, any user who can push branches and open a pull or merge request can trigger the flaw.

As a workaround for this flaw, servers that cannot upgrade yet can add conflict-marker-size=7 to each repository's info/attributes file, or turn off those merge checks for untrusted repositories.



from The Hacker News https://ift.tt/qZW0TXi
via IFTTT

SGLang RCE Exploit Breaches NEAR AI, Steals Data From 18 Agents and About 100 Users

An attacker exploited a remote code execution flaw in SGLang, an open-source inference engine, and ran code on one of NEAR AI's inference servers last Sunday.

The attacker could also have seen requests being processed on that server that day, including requests sent in confidential mode, the company said earlier this week. That mode processes requests inside a trusted execution environment (TEE) designed to keep them private even from the company itself.

But the TEE "does not protect against a vulnerability in the software running inside the environment," the company said. SGLang runs inside the TEE, which is how the attacker could reach requests there.

That access has since been closed, but not before the attacker moved further into the company's systems.

The attacker reached an internal system behind Private Chat, a product the company had already deprecated. So far, the company has confirmed that the attacker downloaded account details for about 100 users there. These are email addresses and names, and for some accounts, plan and balance information.

The company found no sign that stored Private Chat conversations or uploaded files were accessed.

The attacker also reached 18 AI agents on an older deployment of NEAR AI Agents that did not run inside the company's TEE. From those agents, the attacker took data including chat history, settings and logs.

Two customers' NEAR AI Cloud API keys were exposed in logs. The company has revoked both.

After detecting the attack, the company revoked all active sessions and administrator credentials, replaced all agent tokens and took Private Chat offline. It also deployed a fix for the SGLang flaw on all of its inference servers, rotated its remaining credentials and completed a full forensic review, according to its incident report.

Access to its NEAR AI Cloud service has been restored. The company reported the flaw to the SGLang project. It has not identified the flaw by CVE number, named the affected SGLang versions, or said whether the project has released a fix.

The company has contacted users whose account details or agents it confirmed were accessed. Affected users heard directly from security@near.ai, with the steps that apply to them. As a precaution, the company asks users to be careful with messages about their account or balance that they did not ask for.

In a follow-up post yesterday, it said users who have not heard from it do not need to do anything. It has not said whether people whose requests passed through the affected server last Sunday were among those contacted.

In an October 15 technical write-up, Brave, the browser maker, said its Leo assistant runs chats with the GLM 5.3 Flash model inside a TEE operated by NEAR AI.

NEAR AI has not said whether the affected server handled any of those chats.



from The Hacker News https://ift.tt/qs1W0gl
via IFTTT

Hackers Exploit Critical Xen Orchestra Auth Bypass Flaw to Gain Admin Access

French software company Vates VMS has warned of a critical security vulnerability in Xen Orchestra that it said is being actively exploited in the wild.

The authentication bypass flaw, which does not yet have a CVE identifier, is tracked as VSA-2026-062.

"REST cookie parsing turns authenticationToken=j:%7B%7D into {}," Vates VMS said in an alert. "REST authentication passes that object to the XO token provider without requiring a string."

"The token collection treats {} as an unfiltered lookup and returns its first token; the provider authenticates as that token's owner if it is unexpired. The authenticated /rest/v0/users/me/authentication_tokens route then returns reusable login token IDs."

In other words, the vulnerability can allow an attacker to bypass authentication by sending a specially crafted cookie and perform arbitrary actions with "Admin" privileges, ultimately resulting in arbitrary code execution on managed pools and a full XCP-ng node takeover as root.

Vates VMS said it's seeing the vulnerability being actively exploited by a threat actor from the following IP address and TOR domain -

  • 91.211.251[.]112:8001, which has been flagged as a RedLine Stealer command-and-control (C2) server on VirusTotal
  • ustar3rqxgnskzgnwkgpofgtvxevm6cx3lxdbwt4mndtveqyaohid[.]onion:3333

It's unclear when the activity started and if the vulnerability was exploited as a zero-day.

Cybersecurity

Other indicators of compromise are listed below -

  • HTTP requests containing authenticationToken=j:%7B%7D or authenticationToken=j:{}
  • A running virtual machine named pivot2
  • Virtual machines configured using "hvm_serial: file" parameter
  • Suspicious files named /etc/cron.d/zz-ustar2, /etc/cron.d/zz-ustar, /.ustar5, and /.ustar6

The issue has been addressed in Xen Orchestra 6.9.1 and 6.10.0 for the stable and latest channels, as well as xo-server versions 5.211.2 and 5.213.1. If immediate patching is not an option, the following mitigations are advised -

  • Avoid exposing Xen Orchestra instances on the internet
  • Block the IP address and domain associated with malicious activity
  • Block the empty token in a web application firewall (WAF) or a reverse proxy
  • Rotate all passwords and secrets in Vates VMS if indicators of compromise are detected

Filip Magic (@mad31k) and Christoffer Olsen from TDC NET Security have been credited with discovering and reporting the flaw.

Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.



from The Hacker News https://ift.tt/NhZxkHR
via IFTTT

Three China-Nexus Espionage Campaigns Linked Through Sparrow Malware Ecosystem

Three distinct threat activity clusters with shared infrastructure and malware code similarities have been observed targeting telecommunications providers, government organizations, military entities, research institutions, and critical infrastructure across Latin America, Asia, and Europe over the past year.

Check Point Research is tracking the clusters under the names SilentDelivery, OceanGate, and DarkWire. Although initially assumed to be independent sets of attacks, each with its own backdoors and post-exploitation tooling, they have all been linked through a malware ecosystem called Sparrow.

The entity behind the Sparrow framework has been codenamed CopperDragon, and is assessed to be a digital quartermaster developing tools for China-nexus threat actors, including FamousSparrow, Earth Estries, Tropic Trooper, UAT-9244, and UAT-8302.

"Each cluster employed a different toolset and different initial access techniques, including compromising internet-facing infrastructure and highly selective watering hole attacks," Check Point said in a technical report published today. "The compromised websites that were used for watering hole attacks were of government, shipping, and IT and research sectors."

Attacks mounted by FamousSparrow are known for deploying backdoors like SparrowDoor (and its variants Crowdoor and TernDoor), SparroWocky, and HemiGate. It's also assessed to share some degree of overlap with Salt Typhoon. However, the precise nature of the relationship remains unclear.

The cyber espionage ecosystem linked to CopperDragon is driven by three prominent clusters -

  • SilentDelivery (Beginning in early 2026), which conducts highly selective watering hole attacks targeting Europe and Asia that distribute a backdoor called SquadC (aka SquawkDoor) through trojanized MSI installers masquerading as certificate repair utilities
  • OceanGate (2025-2026), which primarily focuses on Asian organizations with a variant of SparrowDoor after obtaining initial access via internet-facing Linux servers and then moving laterally into Windows environments
  • DarkWire (Mid 2025), which targets telecommunications providers and government organizations across Latin America using backdoors called CopperDoor (aka SparroWocky) and CopperDNS

SilentDelivery

The SilentDelivery chain begins with the attacker injecting heavily obfuscated JavaScript into legitimate websites frequented by their intended targets. Visitors to the sites are greeted by a Google Chrome SSL certificate warning that instructs users to install a "Certificate Fix" utility to restore access.

The so-called utility, once deployed, delivers either SquadC or a SparrowDoor variant. All the compromised websites have been found to be related to government, shipping, IT, and research sectors in the Czech Republic, Germany, France, Taiwan, Nepal, Hong Kong, and Indonesia.

According to a report published by Positive Technologies in August 2026, there are indications that the campaign has also targeted entities in Egypt and the Philippines using this method.

"The JavaScript injected into the compromised websites is heavily obfuscated using jsjiami, a publicly available JavaScript obfuscation service," Check Point said. "It first checks whether the user is running Windows and, in some cases, verifies that the website’s domain matches the intended compromised domain."

The script then repeatedly sends status-check requests to a command-and-control (C2) server to fingerprint the user based on IP and geolocation, and ultimately decide whether to continue the attack and serve the fake warning.

Source: Positive Technologies

Written in C/C++, SquadC is a Windows backdoor that enables initial foothold over the infected host. It establishes persistence by means of a Windows Registry Run key that masquerades as a Windows update assistant. Further analysis has uncovered that the malware is also distributed via phishing emails targeting Indonesian organizations.

The phishing email comes with a Windows Shortcut (LNK) disguised as a PDF document, which, when opened, abuses the legitimate "ftp.exe" binary to run a batch script that's responsible for displaying an empty file as a decoy, while launching SquadC via DLL sideloading.

OceanGate

The OceanGate operation, on the other hand, has been observed targeting both Windows and Linux environments, deploying previously undocumented tooling to maintain access, move laterally across the network, and exfiltrate sensitive data.

The Linux phase of the attack involves two new backdoors -

  • AnnobinDoor, a Go-based backdoor that supports remote access, interactive shell, file management, SOCKS proxying, SSH tunneling, port forwarding, and reverse connections.
  • SparrowShell, a modular Linux backdoor that shares overlaps with its Windows counterpart, SparrowDoor

"After harvesting credentials from multiple users and establishing a strong foothold in the Linux environment, the actor moved into the Windows environment," Check Point explained. "The actor attempted to log in to several Windows machines over RDP, trying different passwords until it successfully authenticated with an administrator account."

This step is followed by the deployment of bespoke post-exploitation tools and a variant of SparrowDoor -

  • CopperAdu, a post-exploitation tool which configures a compromised Windows machine for remote administrative access
  • CopperList, a Windows reconnaissance tool for collecting host information, disk details, and a recursive file inventory, including file paths, sizes, and timestamps
  • CopperLogger, a Raw Input-based keylogger to capture keyboard input events, along with monitoring clipboard activity, active window titles, and associated process names and paths
  • CopperLsa, a utility that collects passwords, hashes, and authentication tokens from NTLM and Kerberos

What's more, the threat actor has been found incorporating kernel rootkits and kernel-level access capabilities into SparrowDoor and SparrowShell to evade defenses through process hiding and to capture and manipulate network packet capture using WinDivert drivers.

"The actor abused the driver to convert SparrowDoor into a passive backdoor that intercepts and manipulates packets at the kernel level, making its traffic less visible," Check Point said. "This allows the backdoor to listen internally on one port while receiving connections through an externally accessible port, such as 443, that is already used by a legitimate service."

"The backdoor applies a strict filter to intercept connections from a specific source IP address to the legitimate service's port. It manipulates the packet and rewrites the destination port to the backdoor’s internal listening port, typically a high port such as 49628. For response traffic, it rewrites the source port back to the external service port, making the responses appear to originate from the legitimate service."

Interestingly, SparrowShell shares code- and infrastructure-level similarities with a malware called Mélofée that was first described by ExaTrack in March 2023 as based on the open-source Reptile rootkit. This has raised the possibility that CopperDragon is also behind the development and supply of Mélofée.

DarkWire

The third and last cluster of activity centers around Latin America, with a particular focus on telecommunications operators and government entities. These attacks led to the deployment of two newly identified backdoors called CopperDoor and CopperDNS as a possible replacement for SparrowDoor.

Also supporting these operations is a set of custom tools -

  • CopperLoader, a reflective loader typically deployed through DLL sideloading and is used to deliver additional tools, including CopperDoor, CopperDNS, CopperProxy, and CopperLsass
  • CopperDoor, a memory-resident modular backdoor
  • CopperDNS, a CopperDoor variant that communicates through DNS tunneling using MX queries
  • CopperProxy, a SOCKS5 proxy
  • PyProxy, a lightweight UDP relay written in Python
  • CopperLsass, a dedicated module for dumping the LSASS process for credential harvesting

"The operation heavily relies on DLL sideloading as a primary execution technique, often abusing executables that are not widely observed among other threat actors in the wild," Check Point said. "To minimize their footprint, the operators deliberately avoided creating new directories on disk, instead placing their tools within existing system paths."

"CopperDoor infrastructure demonstrated a higher level of operational security. Most IP addresses were located in Latin America, often within the same country as the victim organization. This proximity likely helps the malicious traffic blend in with legitimate network activity and reduces the chances of detection."



from The Hacker News https://ift.tt/Kmz3yLi
via IFTTT

Blind Eagle Uses Fake Court Notices to Deliver Remote Access Trojan Across Latin America

The threat actor known as Blind Eagle has resurfaced with a new campaign targeting organizations in Latin America through judicial and administrative-themed phishing lures to deliver a remote access trojan (RAT) that shares its lineage with AsyncRAT and DCRat.

"The campaign uses Portuguese and Spanish lures that resemble court notifications, fiscalía notices, tutela proceedings, and administrative documents," Zenox said in a report shared with The Hacker News.

Assessed to be a Spanish-speaking group and active since 2018, Blind Eagle (aka APT-C-36) has a track record of using spear-phishing lures to distribute commodity RATs like AsyncRAT, BitRAT, Lime RAT, NjRAT, Quasar RAT, and Remcos RAT.

Attack chains begin with phishing emails targeting individuals who handle cases, contracts, judicial, or institutional service requests to trick them into opening a malware-laced attachment.

One email containing a Colombian judicial-themed XHTML file has been identified as a weaponized Scalable Vector Graphics (SVG) image that renders a bogus web page impersonating Colombia's Fiscalía General de la Nación, also referred to as the Office of the Attorney General.

The web page, for its part, employs a technique known as HTML smuggling to assemble the next-stage ZIP archive payload locally in the web browser using ZipCrypto, thereby circumventing email security controls.

Present within the ZIP archive is a JavaScript dropper that masquerades as Network Configuration Auditor version 2.7.298. The JavaScript code conducts environment reconnaissance, and collects details such as system version, network profile, installation date, memory size, computer name, environment variables, and directories localized in Portuguese and Spanish.

Upon execution, it launches a Visual Basic Script that performs Windows Antimalware Scan Interface (AMSI) and Event Tracing for Windows (ETW) bypass, while displaying a fake criminal-citation page as a distraction mechanism.

In parallel, the malware also takes steps to delete the original XHTML artifact, clears Mark of the Web (MotW) metadata, and sets up persistence on the host under the Windows Startup folder so that it's automatically executed on system startup.

The attack culminates with the use of PowerShell to decode and launch the final RAT payload in memory. The trojan is an AsyncRAT fork with DCRat lineage based on code structure, configuration, build characteristics, and observed behavior.

Although there is no evidence that these attacks have been successful against real-world targets, a successful compromise could result in environment reconnaissance, document collection, remote access, keystroke and screen capture, surveillance, and data exfiltration over an encrypted channel.

"The targeting of judicial, fiscal, administrative and educational organizations gives the operation access to highly sensitive legal, financial and institutional information," Zenox said.

"Combined with the Portuguese and Spanish lures, Brazilian infrastructure, operational timezone and regional victimology, these elements establish the campaign as an APT-C-36 operation conducted through a Brazilian operational cluster."



from The Hacker News https://ift.tt/xBWmvfg
via IFTTT

Fireworks AI Breach Widens to Expose Customer Billing Data and Incomplete Model Weights

Fireworks AI disclosed on Monday that its investigation into a security incident first reported early last month uncovered further malicious activity, affecting account and billing information, alongside secrets, datasets, and incomplete models for a "limited set of accounts."

In a notice published on October 10, 2026, the company said it detected unauthorized use of internal Fireworks credentials that allowed an unauthorized third-party to access environment variables used in evaluation jobs in a limited number of customer accounts. The activity was detected on October 6, 2026, at 9 a.m. PDT.

At that time, the AI infrastructure provider said it only found evidence that environment variables, including API keys and tokens stored as secrets, were captured in certain affected accounts, adding that there were no signs that customer models, datasets, training data, inference traffic, or personal information were accessed.

In response to the incident, Fireworks AI took the step of revoking the compromised internal credentials and rotating service account tokens, along with affected Fireworks API keys and keys created by the threat actor.

The latest bulletin from the company reveals that the scope of the breach may have been broader than previously thought. The company said attackers reached its development environment via an unnamed third-party cloud provider that hosted Fireworks research and development (R&D) machines on October 23, 2026.

"On October 24, the unauthorized third party used it to reach Fireworks development machines and then run an unauthorized workload that led to additional customer data impact," it added. "As of October 25, we have not detected further evidence of successful unauthorized access by the threat actor on the Fireworks platform customers use."

The breach is said to have provided access to the following types of information -

  • Resource metadata: Fireworks resource identifiers, display names, descriptions, and creation time
  • Billing information: billing and shipping addresses, invoice and payment history, account balance, and credit usage
  • Model weights and datasets: a subset of incomplete model weights and datasets for certain customers

Fireworks AI said payment card numbers are not stored by Fireworks and were not impacted by the security incident. It also said it's alerting customers whose data was impacted.

The company also noted that it has implemented security hardening procedures, such as credential revocation and rotation; isolating affected systems to prevent further unauthorized activity and lateral movement; tightening access controls; and improving its logging and monitoring systems.

"The evidence indicates links to a cybercriminal threat actor group, which is financially motivated and aimed at selling tokens from unauthorized access to large language models (LLMs) to illicit routing gateways," it said.

The activity is assessed to be part of an emerging threat known as LLMjacking, which refers to the act of hijacking a victim's LLM through stolen credentials to fuel a criminal enterprise that thrives on peddling the access to other threat actors, while leaving the legitimate owner to pay the bill.

Last week, Google issued a warning that threat actors are increasingly targeting AI infrastructure for LLMjacking in North America, South America, and Asia Pacific across the financial services, retail, technology, and transportation sectors.



from The Hacker News https://ift.tt/79QX3MG
via IFTTT

Apple Patches iMessage Group Chat Privacy Flaws and Bluetooth Pairing Vulnerabilities

An iMessage flaw could let a remote attacker join a group chat and receive its messages, Apple said yesterday, and it released updates to fix it. The updates also fix a separate iMessage flaw that could let someone added to a group access messages sent before they joined.

As of today, other updates released yesterday for the iPhone XS, XS Max and XR, the iPad (7th generation) and some Apple Watch models do not list either fix.

The company's notes also do not say whether either flaw has been exploited, what an attacker would need, whether group members would see someone who joined this way, or whether every member must update to be protected.

The updates that fix the iMessage flaws also fix a flaw in Google's Brotli compression library. The notes do not mention any attacks using that flaw. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities catalog on October 27.

The flaw that could let a remote attacker join a group chat is tracked as CVE-2026-113961. It is an authorization issue that the updates fix through improved validation. The flaw involving earlier messages is CVE-2026-113960.

Which Updates Carry the Fixes

Each operating system version got its own update. The security advisory for iOS and iPadOS 27.2.1 describes all three flaws. The security releases list links to the notes for every update.

The iOS 18.7.12 notes and the watchOS 26.6.1 notes list other security fixes but not the iMessage or Brotli fixes.

The company does not say whether devices on those versions are affected by the three flaws. Its notes also offer no workaround for anyone who cannot update right away.

The Brotli flaw, CVE-2026-111497, is an out-of-bounds write in the library's decoder that could let malicious input corrupt memory. CISA's catalog entry for the Brotli decoder flaw names Google's Brotli as the affected product and says different products could use the component.

All nine updates fix Bluetooth and AirPlay flaws. Two could allow a malicious Bluetooth device, or an attacker within Bluetooth range, to pair with a device without user interaction. The notes do not say what a paired device could then do.

Two others could let an attacker bypass the limit on pairing code attempts, one from Bluetooth range and one from the same network. Another could let an attacker in Bluetooth range corrupt process memory.



from The Hacker News https://ift.tt/RyxOhkJ
via IFTTT

Russian Turla Hackers Use New Cereal Malware to Steal Emails From Government Exchange Servers

The Russia-aligned state-sponsored threat actor known as Turla (aka Snake) is wielding a previously undocumented cyber espionage toolset called Cereal that's used to break into victims' Microsoft Exchange servers with an aim to surreptitiously collect emails.

According to an ESET report shared with The Hacker News ahead of publication, the sophisticated and modular tool is designed for long-term intelligence gathering and has been observed against two governmental entities in Kazakhstan and Romania in late 2025.

"The Cereal toolset is a carefully constructed instrument for long-term, stealthy cyber espionage," the Slovakian cybersecurity company said. "It leaves little on disk, avoids external infrastructure that could be discovered and blocked, and conceals itself within legitimate Exchange processes."

"The Cereal toolset demonstrates that, for Turla, Exchange servers are not just mail servers – they are durable collection points, internal execution hubs, and a suitable environment for hiding sophisticated .NET tradecraft."

The toolset is a collection of interconnected components that are capable of running on Microsoft Exchange servers, receiving commands, executing them in memory, mapping the infected network, and harvesting emails of interest. The initial access vector used to deliver the malware is unknown, although the group is known to conduct spear-phishing, watering hole, and ISP-level adversary-in-the-middle (AitM) attacks.

Cereal gets its name from the fact that the tools make extensive use of serialization, which refers to the process of converting a data structure or an object's state into a format that can be easily stored, transmitted, and reconstructed.

A number of aspects make the malware stand apart -

  • Absence of an external command-and-control (C2) infrastructure, instead abusing a compromised Exchange server for this purpose.
  • Sending commands in the form of separate, compiled .NET programs.
  • Using an automated email collection module, which is injected into legitimate Microsoft Exchange processes and is engineered to manipulate the email transport pipeline.

The combination of these techniques shows that the threat actor possesses a deep understanding of the internal workings of Microsoft Exchange, ESET added. The Cereal framework consists of eight moving parts that work together to provide the attackers with access to sensitive email data -

  • CerealRunner, which is deployed by the operator and serves as a pathway for dropping additional components, including CerealLoader, CerealSprinter, CerealIron, and CerealMoth.
  • CerealLoader, which loads and runs a .NET assembly from an encrypted file on disk, leading to the execution of CerealSprinter.
  • CerealSprinter, which functions similarly to CerealRunner and is used to decrypt and run CerealNeuron, CerealHermit, and CerealBox.
  • CerealIron, an injector that makes it possible to load and run .NET assemblies from non .NET processes.
  • CerealMoth, which receives an assembly and a method name as inputs, loads the assembly, and runs the specified method.
  • CerealNeuron, a passive backdoor that runs on a compromised Exchange Server and listens for incoming web requests on paths that appear like regular Exchange traffic to execute assemblies contained in CerealRunner binaries.
  • CerealHermit, a variant of CerealNeuron that reads commands from encrypted files on disk and has no network functionality of its own.
  • CerealBox, which is the email harvesting module that processes, filters, and collects email messages by injecting itself into the Exchange transport service ("EdgeTransport.exe").

Upon gaining visibility into the email flow, the malware looks for messages containing DOC, DOCX, or PDF attachments, and matches at least one of many hard-coded lists with sender addresses, recipient addresses, subject lines, or attachment names.

Emails that meet the filtering criteria are compressed, encrypted, and staged in files on disk, after which they are exfiltrated and deleted via CerealNeuron commands.

In the attack aimed at the Romanian government organization, CerealBox is said to have been configured to gather emails involving NATO and European Union institutional addresses, a pattern that aligns with Russia's strategic priorities.

The commands delivered as compiled .NET programs are handled by CerealRunner, which unpacks and executes the payloads in memory and then sends the results back to CerealNeuron for subsequent exfiltration to the threat actor in encrypted format.

The commands support retrieving mailboxes or specific messages; queuing Active Directory for computers, users, groups, and DNS records; running Windows Management Instrumentation (WMI) queries; extracting LSA Secrets; listing volume snapshots; and performing file operations.

"The sheer volume of near-identical binaries, each compiled for a specific task, strongly suggests that the operators have an internal framework that automates the compilation and packaging of commands," ESET researcher Matías Porolli said.

"Combined with a codebase built around modular, interchangeable components, the impression is one of a mature, well-engineered platform – rather than a loose collection of scripts."



from The Hacker News https://ift.tt/zX0SV1y
via IFTTT

SAP Patches Four CVSS 10.0 Flaws, Including Two Enabling Remote Code Execution

Four flaws that attackers could exploit without logging in were fixed today as part of SAP's monthly Security Patch Day—the vendor rates all four 10.0, the maximum CVSS score.

Three are in the SAP NetWeaver application server, the software SAP systems run on, and one is in the Web Dispatcher, which receives web requests from the internet and passes them on to that server.

The flaws in the Web Dispatcher and the Internet Communication Manager (ICM), which handles the server's web traffic, could allow an attacker who can reach the software over the network to run code, the vendor says.

The flaw in the server's SAML 2.0 service provider, which hands off user sign-in to an identity provider, could allow an attacker to log in as any user on some systems that use SAML single sign-on.

The flaw in SAP Gateway, which connects the server to other SAP systems and programs, could allow an attacker to impersonate one of the system's own servers and take unauthorized actions.

None of the four require any user action to work.

Affected Versions and SAP Notes

Each flaw is fixed in its own note, and the affected versions differ by component, according to SAP's November security bulletin. The notes are in SAP for Me, which requires a sign-in, and the vendor strongly recommends applying them as a priority.

CVE Component SAP Note Affected versions
CVE-2026-76964 Internet Communication Manager (ICM), SAP NetWeaver AS ABAP Note 3778530 KRNL64UC 7.53, KERNEL 7.53, 7.54, 7.77, 7.93, 9.16, 9.18, 9.20
CVE-2026-89126 SAP Web Dispatcher Note 3778556 HDB 2.00, KRNL64UC 7.53, WEBDISP 7.53, 7.54, 7.77, 7.93, 9.16, XS_ADVANCED_RUNTIME 1.00, SAP_EXTENDED_APP_SERVICES 1, KERNEL 7.53, 7.54, 7.77, 7.93, 9.16, 9.18, 9.20
CVE-2026-89103 SAP Gateway Note 3798345 KRNL64NUC 7.22, 7.22EXT, KRNL64UC 7.22, 7.22EXT, 7.53, 8.04, KERNEL 7.22, 7.53, 7.54, 7.77, 7.93, 8.04, 9.16, 9.20, 9.21
CVE-2026-120017 SAML2 service provider, SAP NetWeaver AS ABAP and ABAP Platform Note 3849308 SAP_BASIS 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 758, 816, 920, 921, 922

What Each Flaw Allows

On the affected SAML setups, an attacker could use CVE-2026-120017 to log in as privileged users too, according to the vendor. A full compromise could follow, possibly reaching connected systems.

A different SAML flaw in the same software, CVE-2026-44748, was fixed on June 9 and needed an attacker with a normal user account.

In the ICM flaw (CVE-2026-76964) and the Web Dispatcher flaw (CVE-2026-89126), crafted network traffic could corrupt memory. An attacker who succeeds could then run code and fully compromise the system.

SAP Gateway uses access control lists to decide which outside programs may connect to it and which programs it may start. In CVE-2026-89103, the gateway enables its default list with high privileges, allowing an external attacker to be treated as one of the system's own application servers. That attacker could then take unauthorized actions in the application environment.

What to Do

In its Patch Day analysis, RedRays, a company that reviewed the notes in SAP for Me today, advises updating the kernel and all Web Dispatchers in a single rollout. That rollout should reach levels that cover all 17 of this month's kernel and Web Dispatcher fixes.

The firm's guidance for each flaw:

  • SAML2 (CVE-2026-120017). Under certain configurations, the service provider did not check signatures on incoming assertions. Treat any AS ABAP system that uses SAML2 for browser logon, such as Fiori Launchpad or Web GUI behind an identity provider, as in scope until shown otherwise. There is no workaround, so the correction instructions or the listed support package are the only fix. The firm's SAML2 analysis also suggests reviewing every trusted identity provider in transaction SAML2 and checking audit logs for SAML logons by privileged users from unexpected sources.
  • SAP Gateway (CVE-2026-89103). Where secinfo and reginfo hold no explicit rules, or rely on the internal host keyword, the gateway falls back to rules that allow the system's own application servers. An attacker who passes as one of them could then reach the usual gateway attack paths toward command execution. The note lists no workaround. For kernels up to 7.77, the fix adds the profile parameter gw/acl_mode_proxy, which tightens the default rules, while kernels from 7.93 on already have it. The firm's Gateway analysis advises setting it after patching and checking that gw/acl_mode is 1, that secinfo and reginfo hold explicit rules, and that the gateway port (33xx) cannot be reached from user networks or the internet.
  • ICM (CVE-2026-76964). WebSocket control frames with invalid length fields cause a heap out-of-bounds write before any login. SAP NetWeaver AS Java is not affected, and the fix ships through dw.sar and the SP Stack Kernel. If users reach the ICM only through a Web Dispatcher, patching that Web Dispatcher to the levels in FAQ note 3778788 shields the ICM for now, according to the firm's ICM analysis. That holds only if nobody can reach the ICM ports directly. Turning off WebSocket support blocks the bug as a last resort, but it breaks features that depend on it.
  • Web Dispatcher (CVE-2026-89126). It has the same root cause as the ICM flaw. It affects standalone and embedded Web Dispatchers, including those in SAP HANA XS Classic and XS Advanced, but not SAP Content Server. The firm's Web Dispatcher analysis lists the patch paths: SAPWEBDISP.SAR for standalone instances, dw.sar or the SP Stack Kernel for embedded ones, SPS08 revision 089.05 or SPS07 revision 079.11 for HANA XS Classic, and version 1.5.4 or later for XS Advanced. Turning off WebSocket support works until the patch is in, but the note warns that this affects ABAP Push Channels and some Fiori features. Find every Web Dispatcher first, because one missed instance leaves the flaw open.



from The Hacker News https://ift.tt/29IueST
via IFTTT

France Blames Iran for Sabotage Attack on Refrigeration Controllers at About 700 Retail Sites

An October cyberattack on refrigeration controllers at about 700 French retail sites was carried out by a cyber unit of Iran's Islamic Revolutionary Guard Corps (IRGC), the French government said yesterday.

The attackers broke into controllers on the night of October 11 and changed their defrost settings to high temperatures. That caused food losses and, in at least 15 cases, fires.

The unit is called Shahid Kaveh. It is known mainly through hacktivist personas, such as CyberAveng3rs and Cyber Isnaad Front, that publicly claim some of its attacks, France says.

France's Foreign Ministry plans to summon Iran's ambassador and to ask its European partners to adopt new sanctions against Iranian organizations and individuals involved in the attack.

The Paris prosecutor's office opened a judicial investigation yesterday against the unit's head, the head's two deputies and anyone else identified. It has asked for international arrest warrants. The offenses under investigation include illegally interfering with computer systems and causing damage by means dangerous to people, both made more serious by the aim of serving a foreign power, Iran.

In the October attack, the attackers took remote control of Danfoss and Dixell refrigeration controllers through web interfaces, the prosecutor's office said in a press release. They started abnormal defrost cycles with no time limit and switched off the temperature probes' safety alerts, which should go off above a certain temperature. The attack caused about 20 fires.

Most of the organizations hit were large retailers, according to a joint report by France's cyber crisis coordination center, known as C4. They include Casino, Leclerc, Coopérative U, Metro, Carrefour and Intermarché.

Small butcher shops, a slaughterhouse and cooperative food plants were also among the victims.

The center also tied the attack to the simultaneous targeting of Schneider Electric equipment at several small hydroelectric installations in France. The effects on that equipment were moderate.

In its attribution statement, the ministry estimated the food losses at several tens of millions of euros and called the operation the first offensive cyber campaign on French soil carried out purely for sabotage.

How France Tied the Attack to Iran

The C4 brings together France's national cybersecurity agency (ANSSI), the DGSE and DGSI security services, the armament directorate and the cyber defense command. It says four indicators point to the IRGC as the sponsor of the attack and to Shahid Kaveh as the unit that carried it out.

The infrastructure used in the attack was also used during the same period for reconnaissance of Schneider Electric equipment. That equipment is installed at sites such as small- and medium-sized energy and water production sites. The reconnaissance relied on techniques that Shahid Kaveh has used since at least April.

The attackers also used FOFA, a scanning tool they usually use. CyberbanNews, a propaganda outlet linked to the unit, reported on the attack as early as October 13. The attack infrastructure also held traces of Persian.

Prosecutors said the criminal investigation, run by France's anti-cybercrime office (OFAC) and the DGSI, found an attack method typical of the unit. It also found the use of Persian and IP addresses leading to devices located in Iran.

Shahid Kaveh has previously claimed attacks on industrial equipment, according to C4. Through CyberAveng3rs, it claimed an earlier campaign against Unitronics, an Israeli company that makes industrial control systems, in November 2023. In March and April, it claimed a large sabotage campaign against Israeli and U.S. interests that hit industrial control equipment, including Israeli refrigeration equipment.

France's attribution does not mention the new wave of refrigeration attacks that struck supermarkets in several other European countries last week.

What Operators Should Do

France's CERT-FR said in an incident alert that it was aware of numerous compromises affecting remote refrigeration controllers across four product families. They are the Danfoss AK-SM and AK-SC series, the Copeland xweb, and the Dixell xweb.

The alert, last updated on October 16, warned that attack campaigns against this equipment were probably still underway, and that exposing a management interface to the internet goes against good practice.

For controllers that are not compromised, the alert's steps are:

  • Remove internet exposure from these units and from any unit reachable at a public IP address.
  • Check insurance contract terms before cutting off the data feed to the refrigeration contractor.
  • Review the full configuration, especially the defrost ranges.
  • Restore access only through a secure VPN or a protected network. In an emergency, filtering the contractors' IP addresses at a firewall is possible, but it is not a lasting fix.
  • Follow the maker's recommended practices. For Danfoss devices, this includes updating firmware, setting the security level to Strict, and ensuring default passwords have been changed.

For compromised controllers, the steps are:

  • Remove internet exposure and check insurance terms, as above.
  • Restart Danfoss equipment, or otherwise restore the device to its factory settings.
  • Restore access only through a secure VPN or a protected network. As above, firewall filtering of contractors' IP addresses is an emergency option, not a lasting fix.
  • Reconfigure the device before putting it back into service, then follow the maker's recommended practices.

An end-of-life (EOL) device that receives no security fixes faces a very high risk of compromise if it remains exposed to the internet, the alert warns. In that case, a factory reset alone is not enough: it removes the attackers' persistence, but the device stays vulnerable and will almost certainly be compromised again.



from The Hacker News https://ift.tt/vRXuqWC
via IFTTT

Anthropic's Claude Fable 5.2 Beats GPT-6 Cyber in Multi-Stage Cyberattack Benchmark

Anthropic on Monday released Claude Fable 5.2 and Claude Mythos 5.2 models, which it said exhibit improvements in coding, reasoning, and vision.

During pre-release training, the large language models (LLMs) helped its engineers "complete otherwise-infeasible software migrations, designed three working electronic devices from scratch, solved two open problems in the physics of black holes, made substantial progress on robotics evaluations, and formalized the proof of Fermat’s Last Theorem in 30 hours."

The artificial intelligence (AI) company said high-stakes risks arising from misalignment remain low, and claimed the models matched or performed better than Claude Opus 5.5, Claude Sonnet 5.5, and Claude Mythos 5.1 on most alignment measures, resistance to misuse, honesty, and factuality.

"It was roughly an order of magnitude less likely than Opus 5.5 and Sonnet 5.5 to publish harmful content to public package registries without encouragement, though it still did so when encouraged by the simulated user," Anthropic noted in its system card.

On Irregular's CyScenarioBench, which measures whether a model can plan and execute a multi-stage cyber operation in a realistic environment, Fable 5.2 completed 76.3% of all challenges, compared to 61.7% for Fable 5.1 and 61% for OpenAI's GPT-6 Cyber.

In a pair of reports published over the last month, Irregular said Google's Gemini 4 Argon solved 12 challenges in the subset of the CyScenarioBench suite end to end, up from 5 for Gemini 3.8 Flash Cyber and none for Gemini 3.1 Pro.

"On CyScenarioBench, GPT-6 Cyber completed 11 of 11 long-horizon scenarios at least once, compared with 8 of 11 for GPT-6 Astra. Its average success rate was 61%, an increase of 7 percentage points," the AI testing lab said. "On Atomic Challenges, GPT-6 Cyber solved all 22 challenges. Average success rates were 97% in vulnerability research and exploitation, 98% in network attack simulation, and 63% in evasion."

Fable 5.2 also scored 89.6% on the CVE Rediscovery benchmark, Anthropic's own internal evaluation of whether an AI model can independently rediscover known vulnerabilities given only the affected source code. The assessment includes 1,829 advisories for open-source projects published in October 2026.

Describing Claude Mythos 5.2 as its "most capable model for cybersecurity engineering," Anthropic said it can flag more vulnerabilities than prior models, while simultaneously getting better at reproducing and fixing them.

As before, the model's cyber capabilities are accessible through its Cyber Verification Program. Claude Fable 5.2 is available on all platforms, including Amazon Web Services, Google Cloud, and Microsoft Azure.

The development comes as Anthropic updated Claude Security with continuous code scanning and automatic fix tracking to help security teams monitor and address vulnerabilities as code changes.

"Each finding comes with a severity rating, judged against your project's threat model, and an explanation of how an attacker could reach the vulnerable code, so teams can fix what's actually reachable first," Anthropic said.



from The Hacker News https://ift.tt/KsOy7Pq
via IFTTT

N-able Takes N-central Cloud Offline After Researcher Discloses 33 Zero-Days with PoC Exploits

N-able said it has taken N-central Hosted Environments offline and is urging on-premises customers to shut down their servers until further notice following the public disclosure of over 30 vulnerabilities collectively tracked as Able2Shell.

"As a precautionary measure, we are temporarily taking our Hosted N-central environment offline while we take the necessary actions to secure the environment and implement appropriate remediation," N-able said.

"During this time, customers will be unable to access their Hosted N-central classic environment, and associated services may be unavailable. However, the Ecoverse services under N-able Login remain available and online, including Asset View, Patching, Vulnerability Management, scripting, policies and tagging."

The company also said it has not observed any signs of active exploitation of these vulnerabilities, adding it's currently working on a hot fix to address them.

The following services are impacted -

  • N-central (hosted version) (Americas)
  • N-central (hosted version) (APAC)
  • N-central (hosted version) (Europe)
  • N-central On-premise (Americas)
  • N-central On-premise (APAC)
  • N-central On-premise (Europe)

The development comes as independent security researcher Sean Bales disclosed multiple security flaws along with proof-of-concept (PoC) exploits. The researcher said the issues were tested against N-able N-central Appliance 2026.4.0.31.

The identified zero-day vulnerabilities include credential disclosure, arbitrary file writes, directory traversal, cross-site scripting (XSS), XML external entity (XXE) injection, and remote code execution (RCE) flaws -

  • Multiple N-central zero-days enable anonymous credential theft, administrator creation, and nable/root RCE.
  • Chains include XXE/NCI trust abuse, support-token theft, unsigned NSP execution, XSS-to-OGNL, and authenticated reverse shells.
  • Arbitrary file writes, traversal, credential disclosure, MDM impersonation, audit tampering, and privileged-helper injection.
  • A native GenericTCP stack overflow also achieves root command execution

Successful exploitation of these flaws can allow rogue administrative access to the N-central management interface and facilitate command execution as root.

(This is a developing story. Please check back for more details.)



from The Hacker News https://ift.tt/90oxdhG
via IFTTT

CISA Warns of Active Exploitation of OpenSSH, GPUStack, FreeSWITCH, and IBM Flaws

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday added four security flaws impacting GPUStack, SignalWire FreeSwitch, OpenBSD OpenSSH, and IBM Aspera Faspex to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation.

The vulnerabilities are listed below -

  • CVE-2026-123218 (CVSS score: 9.8) - An incorrect authorization vulnerability in IBM Aspera Faspex that could allow an authenticated user to craft a specific message to bypass authorization, causing privilege escalations. (Fixed in November 2026)
  • CVE-2026-116779 (CVSS score: 9.8) - A code injection vulnerability in SignalWire FreeSwitch that could result in configuration and credential disclosure, arbitrary call control, and command execution. (Fixed in October 2026)
  • CVE-2026-123158 aka SSHole (CVSS score: 8.1) - An unexpected status code or return value vulnerability in OpenBSD OpenSSH on Linux that could allow for authentication bypass. (Fixed in November 2026)
  • CVE-2026-102895 (CVSS score: 9.8) - An improper authentication vulnerability in GPUStack that could allow improper authentication vulnerability which could allow unauthenticated administrative access, including user and model changes, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution through POST /v2/inference-backends/from-yaml. (Fixed in July 2026)

The addition of CVE-2026-123158 to the KEV catalog follows reports of exploitation attempts targeting the flaw since November 6, 2026. A total of 22 exploitation attempts have been recorded from 14 unique IP addresses so far, according to Previdian.

In a post shared on X on November 7, 2026, Defused Cyber said it "observed a small amount of actors targeting SSHole" but stressed the exploitation activity is not widespread yet.

According to GreyNoise, the first exploitation attempt against its honeypot network was observed on November 7, 2026, at 12:46 a.m. UTC. Confirmed post-exploitation activity has been detected from six source IP addresses, representing 18 distinct attack chains to date.

These involve reconnaissance, queries to cloud metadata services, attempts to read password hashes and root SSH keys, and efforts to modify the SSH authorized_keys file to gain persistent access.

In at least one case, unknown threat actors have been observed deploying TAC Agent, a Python-based command-and-control (C2) agent capable of shell command execution, system reconnaissance, directory enumeration, file transfer, and updating itself.

Threat intelligence firm watchTowr said it has also observed the OpenSSH flaw being weaponized in the wild for botnet and cryptocurrency miner activity.

In an advisory for CVE-2026-102895 published on July 31, 2026, the maintainers of the GPUStack Python package credited Nikko Enggaliano, Wei Yunzhou, Rui Yang, and Haoyu Wang for independently reporting the flaw, adding that "active in-the-wild exploitation" was reported by Ulex Innovative Systems' Javier Sixto.

There are currently no public reports on how the other vulnerabilities are being exploited, who is behind them, and the scale of such efforts. Federal Civilian Executive Branch (FCEB) agencies are recommended to apply the fixes by November 12, 2026.



from The Hacker News https://ift.tt/ZwLJN3b
via IFTTT

Monday, November 9, 2026

FORGE Lab uses agentic tools to identify memory safety issues in Rust

Microsoft’s FORGE Lab found several memory safety issues in Rust’s standard library (std and core), including cases where code written entirely in safe Rust can trigger undefined behavior. The research used Hyenas, FORGE’s frontier research version of codename MDASH, an AI-powered vulnerability-scanning system. The findings reveal three recurring patterns of misplaced trust in unsafe code: trusting code not to panic, trusting user-provided implementations to be correct, and trusting the underlying system.

Rust’s safety guarantees are precisely what make these findings interesting. Its rich type system and ownership model rule out whole classes of memory-safety issues, but much of the standard library relies on unsafe code underneath its safe APIs. When that code breaks its safety contract, even safe Rust can encounter behavior the language is designed to prevent.

Rust’s memory-safety guarantees are increasingly important as the language becomes part of software that billions of people rely on every day. Billions of people are estimated to interact with Rust-based software or operating systems daily, often without knowing it. Microsoft made Rust a Tier-1 internal language alongside C++, C#, and TypeScript, GitHub rewrote the Copilot agent runtime in Rust, and Bun, Android, the Linux kernel, and Cloudflare are moving code to it as well. Much of this software relies on Rust’s foundational libraries, core and std, and the safety guarantees of the APIs they provide. Bugs in those libraries can have consequences well beyond the code where they originate.

Unsafe Rust has been a long-running interest for us. Our team includes the people behind Rudra, a static analyzer that looked for memory-safety bugs across the Rust ecosystem in 2021. We also write many of our own tools in Rust, so its safety is more than a research topic for us. This year, we took a closer look at the standard library to see what kinds of mistakes still show up in its unsafe code today.

In this post, we share some of the bugs we reported to the Rust issue tracker. We use them to discuss what Rust does and doesn’t guarantee, why writing correct unsafe Rust is so difficult, and why Rust’s safety model still matters even though its memory safety isn’t perfect.[OW1] [YB2]

How we found and validated the bugs

At Microsoft FORGE Lab, we study vulnerabilities in complex software, including the Rust standard library. Our team combines years of experience in vulnerability research with AI-assisted tools that help us investigate code and find bugs that are difficult to uncover through traditional analysis alone.

Some of the bugs in this post were found with help from Hyenas, our research version of codename MDASH. Our researchers investigated the underlying code, reproduced the bugs, assessed their potential security impact, and worked with Rust maintainers to report and fix them.

This post focuses on soundness bugs in the standard library’s unsafe code. Bugs in the compiler itself, such as miscompilations and holes in the type system, are a different topic that we don’t cover here.

A note on open issues

At publication, two of the issues reported by our team remain open. The article also references related issues reported by others and fixes that are still under review. The Rust maintainers triaged and responded to our reports quickly, and we believe maintainers and the contributors working on these issues are doing their best and making the right tradeoffs among the many bugs they handle.

If you’re interested in an open issue, please comment only when you have something genuinely new to contribute, such as new information or an affected real-world use case.

Patterns of Rust’s Safety Bugs

At the lowest level, Rust uses unsafe blocks to work with raw pointers and interact directly with the operating system. Much of the standard library, including Vec and String, is built from small unsafe pieces wrapped in safe APIs. Inside an unsafe block, the programmer takes responsibility for the guarantees the compiler can’t check, and that responsibility extends to the safe API built around it. That API must be sound: no matter how safe code uses it, it must be impossible to trigger undefined behavior.

Upholding that promise is harder than it looks. Consider a function that returns the byte at idx from any type that can be viewed as a byte slice, skipping the redundant bounds check after doing its own:

pub fn get


from Microsoft Security Blog https://ift.tt/O52PC0U
via IFTTT

Hackers Exploit Qubole's Trusted AWS Access to Breach Customer Accounts and Steal Data

An attacker broke into AWS accounts belonging to multiple Qubole customers between October 14 and October 26 and stole stored secrets and data, cloud security company Wiz said today.

The attacker used credentials for an AWS account that Qubole's platform uses to reach those customers. How the attacker got those credentials has not been disclosed.

Qubole, a data lake platform owned by Idera, operates within its customers' AWS accounts. To let it in, a customer creates an IAM role, which is an AWS identity with its own set of permissions.

The role's trust policy allows Qubole's AWS account to assume the role, granting those permissions. Each request to do this, called AssumeRole, must include a matching code from Qubole known as an External ID.

Apart from the attack, most of the roles the attacker assumed were unused, according to Wiz's researchers. But each role still trusted Qubole's account, so the attacker's requests worked.

Any organization that has connected Qubole to AWS, even one that no longer uses it, should check its CloudTrail logs from October 1 onward. The sign to look for is an AssumeRole request from the account Qubole's platform uses, 805246085872, that came from an address outside AWS.

The researchers did not say whether the credentials have since been disabled or whether the activity has stopped. Neither Qubole nor Idera had posted a statement about the attack on their websites when The Hacker News checked today.

Why the Roles Let the Attacker In

Every AssumeRole request tied to the attacker carried an External ID and was accepted, the researchers said in their technical analysis.

AWS accepts an AssumeRole request for such a role when it comes from the trusted account and includes the correct External ID. The code is not treated as a secret, and anyone with access to the role can view it, according to AWS's external ID guidance.

Sentra spotted the activity in several of its customers' environments and alerted the researchers.

In the accounts the researchers examined, the attacker looked for stored credentials. It read environment variables for Lambda functions, pulled secrets from Secrets Manager, and read values from the SSM Parameter Store.

It then ran the credentials it had found through TruffleHog to test whether they worked. These were the victims' own AWS access keys, Entra ID client secrets, and Okta client credentials.

The attacker also copied data out of S3. It retrieved data from any bucket a role could access rather than searching for specific data, and sometimes downloaded an entire bucket in a single session.

The researchers have not linked this campaign to any other publicly reported activity, and say the targeting does not match what state-backed groups usually go after.

Qubole also lets customers connect with AWS access keys instead of a role. From October 8 to October 11, an attacker used customers' own AWS access keys, which the researchers believe had been set up for Qubole.

That attacker then compromised a few of the victims' cloud environments. This activity has not been linked to the AssumeRole abuse.

How to Check Your Accounts

Wiz's hunting guidance covers CloudTrail logs from October 1 onward in every AWS account that holds a Qubole role. Look for:

  • Account: AssumeRole requests where userIdentity.accountId is 805246085872 and sourceIPAddress is not an AWS address. The researchers saw Qubole's real traffic come only from AWS.
  • IAM principal ID: AIDA3W7DIFLYOLTK63SFS. Any activity from this IAM user should be investigated, because only the attacker used it in the accounts the researchers examined.
  • IAM principal ID: AIDAJYRRH5Y3A7AAJM2HW, when the source address is outside AWS. The attacker used this IAM user from October 18, but Qubole's normal traffic also uses it.
  • IP: 57.129.54[.]120 and 2001:41d0:70d[:]7800::, OVH-hosted addresses that the attacker used.
  • IP: 45.83.220[.]211, 185.209.199[.]73 and 89.37.63[.]175, which are Mullvad VPN addresses. Other VPN users share them, so a match alone is not proof.
  • Session name: role sessions that start with quiam-, such as quiam-enum.
  • User agent: TruffleHog on GetCallerIdentity calls from one of the IP addresses above. Look for the same user agent in your identity provider's sign-in logs.

For every suspicious session, review everything it did afterward, especially in Secrets Manager, SSM Parameter Store, Lambda, and S3.

CloudTrail management events log each AssumeRole request and bucket listing, but not which S3 objects were read. That needs S3 data events or S3 server access logs. Several victims lacked the required logs, so responders could not determine which objects the attacker had read.

How to Close the Route

The researchers recommend these steps:

  1. If the attacker assumed one of your Qubole roles, rotate all secrets, parameters, and Lambda environment variables that role had access to, and revoke the role's active sessions. Rotating a credential does not end sessions that were already issued.
  2. Remove any Qubole role you no longer need, or take Qubole's account out of its trust policy.
  3. Where Qubole supports it, swap the account-wide :root principal in the trust policy for the specific IAM principal that Qubole uses.
  4. Add an aws:SourceIp or aws:SourceVpce condition that limits AssumeRole requests to the vendor's documented network ranges. In this attack, the researchers said, "a source IP condition alone would have blocked every role assumption we observed."
  5. Assume others can see the External ID. It is logged in plain text in CloudTrail, and vendors and infrastructure-as-code files often store it, so do not use it as your only control. After an incident like this, change it to Qubole and use a different value for each role where possible.
  6. Review what each vendor role can reach. Qubole's setup guide includes a sample S3 policy that lets the role read every bucket in the account. Vendor roles are often granted access to Lambda settings, Secrets Manager, SSM parameters, and broad S3 read permissions for convenience, according to the researchers.
  7. Set alerts for AssumeRole requests from a vendor account that arrive through a VPN or a hosting company the vendor has not used before.
  8. Log every account and region with an organization trail, and enable S3 data events or server access logs for buckets that store sensitive data.



from The Hacker News https://ift.tt/Qjdbnz3
via IFTTT

Bitter Hackers Deploy New PapRAT Backdoor in Cyberespionage Campaign Targeting South Asia

The South Asian cyber espionage group known as Bitter (aka APT-C-08, APT-Q-37, Hazy Tiger, Orange Yali, T-APT-17, and TA397) has been observed targeting South Asian organizations with a previously unreported remote access trojan called PapRAT.

"PapRAT has both C++ and Rust implementations," Fortinet FortiGuard Labs researcher Cara Lin said. "Its capabilities include command execution, file uploads and downloads, file deletion, directory and drive enumeration, and screenshot capture. The Rust variant adds PowerShell execution and other commands."

The campaign is notable for making use of three different infection chains -

  • A Windows Shortcut (LNK) file that abuses the native "ftp.exe" utility to run scripts and create scheduled tasks designed to maintain contact with a command-and-control (C2) server.
  • A VHDX disk image containing a LNK file that launches a lure Microsoft Excel spreadsheet, while running an MSI installer in the background to deploy PapRAT.
  • A URL shortcut (URL) file that fetches a LNK file via WebDAV, which then leads to an MSI installer that deploys PapRAT.

The living-off-the-land (LotL) approach is designed to execute commands from a remote server ("goodnfortunes[.]com"), allowing it to collect directory and task lists, directory information from Desktop, Documents, and Downloads, installed antivirus product data, and mounted drives.

The harvested reconnaissance information is saved as "abc.pdf" and exfiltrated back to the C2 server via a curl command, after which the staged file is deleted from the host.

A second version of the script has been found to retrieve a file called "talk.log" from "techtalkhelp[.]com." The payload contains a Base64-encoded script to obtain additional instructions from the same server and execute them as PowerShell commands.

"This staging model gives the attacker operational flexibility, while the commands are updated server-side without pushing a new binary, avoiding PE drops and process injection that some security appliances could easily detect," Fortinet said.

The PapRAT malware delivered via the MSI installer in the second attack chain is designed for remote control. It supports eight commands -

  • MSG, for remote shell
  • FDD, for directory listing
  • DEL, for file deletion
  • RUN, for arbitrary file execution
  • GDR, for drive enumeration
  • SS1, for screenshot capture
  • UPP, for uploading local files to the C2 server ("rivingtonclarks[.]com")
  • DWW, for downloading files from the C2 server

A Rust version of the malware incorporates three more commands -

  • MS2, for PowerShell command execution
  • SLP, for sleeping and polling resumption
  • BYE, for process termination

A notable aspect of the third attack chain is that it combines the salient aspects of the first two sequences by using a script to download an MSI installer via curl. Like before, the MSI installer serves as a conduit for PapRAT, which then proceeds to drop WmRAT, a malware previously identified as used by Bitter.

The findings indicate that the threat actor continues to refine its custom arsenal to establish and maintain access to targeted systems.

"These changes underscore the importance of monitoring malicious behavior across scripting tools, scheduled tasks, and installer activity alongside detecting known malware signatures," Fortinet said. "Organizations should treat unexpected LNK files, URL shortcuts, disk images, and MSI packages with caution, particularly when delivered through unsolicited messages."



from The Hacker News https://ift.tt/G8C7MWn
via IFTTT

⚡ Weekly Recap: SSHole Exploited, APT Root RCE, Robot Takeovers, 15K Hacked Sites, and More

A system doesn't always need a complicated bug to let someone in. Sometimes, a blank password is enough. That's one of the bigger stories this week. And it gets worse when the tools meant to keep systems updated or running safely become part of the attack.

Elsewhere, attackers are hiding inside normal web traffic, stealing credentials from network devices, and finding new uses for exposed systems. AI is helping some of them move faster, but old mistakes are doing plenty of the work too. Even forgotten settings and small changes made months ago are coming back to cause trouble.

There's a lot packed into this week's news, including some strange research findings, fresh attacks, and a few warnings worth taking seriously. Here's the full recap.

⚡ Threat of the Week

OpenSSH Flaw Sees Exploitation Attempts — Threat actors are attempting to exploit a recently disclosed security flaw impacting OpenSSH that can enable sign-ins to accounts that have no password set. The vulnerability, tracked as CVE-2026-123158 (CVSS score: 8.1) and codenamed SSHole (or *sshole), impacts Linux systems that run OpenSSH on the musl C library with Pluggable Authentication Modules (PAM) disabled, including Alpine Linux's default OpenSSH server configuration. As of November 9, 2026, a total of 20 exploitation attempts have been recorded from 13 unique IP addresses from Denmark, Iran, Japan, the Netherlands, Norway, Singapore, Sweden, Switzerland, and the U.S.

🔔 Top News

  • Trojanized CWP Web Server Used to Deliver CWPdoor — A new Linux malware called CWPdoor is being distributed via a trojanized version of cwpsrv, the built-in daemon and web server that powers the Control Web Panel. According to XLab, a shell script named "cwpsrv_update.sh" is used to download "cwpsrv" from a remote server ("136.0.141[.]71") and replace the legitimate file on the system. "The downloaded cwpsrv is a passive backdoor that can be triggered by specific headers in HTTP/HTTPS traffic to remotely execute commands specified by the attacker," XLab said. "Its backdoor logic is triggered only when it receives a specially crafted request from the attacker. At the same time, it suppresses logging for that request, leaving no trace of the interaction in the access logs. This combination of directly replacing the legitimate cwpsrv binary, passive triggering, and log suppression makes CWPdoor exceptionally stealthy."
  • Debian and Ubuntu APT Flaw Allows Code Execution as Root — A vulnerability in the APT package manager (CVE-2026-109518, CVSS score: 7.7) can be exploited to install a package under certain conditions and achieve code execution with elevated privileges. The issue affects Ubuntu and Debian operating systems. "Under specific conditions, when APT is configured to use HTTP package sources with retry settings enabled, a third-party with a network position between the host and the package mirror can cause APT to install a package that did not pass verification," Amazon said in an advisory. "Maintainer scripts within that package then run with elevated privileges."
  • CERT-In Flags AI-Driven Attacks Targeting Financial Organizations — The Indian Computer Emergency Response Team (CERT-In) has disclosed that an artificial intelligence (AI)-assisted threat actor it tracks as Crafty Falcon is targeting organizations in the Banking, Financial Services, and Insurance (BFSI) sectors in the country. Calling it a "significant escalation" in attacks, the threat actor is said to be re-targeting entities that were originally targeted last month after incomplete remediation, adding that the intrusions "have been timed to coincide with holidays, weekends and other low-monitoring windows to delay detection and response."
  • Zyxel Fixes 0-Day exploited to Hack About 1,000 Network Switches — Zyxel has fixed a zero-day vulnerability in its GS1900 series network switches that threat actors exploited to compromise nearly 1,000 devices worldwide and steal configuration files and credentials. The vulnerability, tracked as CVE-2026-107441 (CVSS score: 8.8), is an out-of-bounds write flaw that could "allow a LAN-based, unauthenticated attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request." The activity has been attributed to a Chinese-speaking threat actor tracked as Kapibala (aka Red Heron). The attacker has been found to weaponize the flaw to deploy the JITTERLY backdoor and SIXZUT, a ring 3 rootkit.
  • cPGuard Update Mechanism Hijacked to Deliver Backdoor — Unknown threat actors compromised the update infrastructure for the cPGuard web security suite to distribute a backdoor and a data-stealing script. "On 2 November 2026 at 02:06 UTC, an unidentified attacker used compromised credentials to gain unauthorized access to OPSSHIELD's update distribution infrastructure (CDN)," OPSSHIELD said. "The attacker used this access to distribute a malicious script through the cPGuard update channel." The attacker is said to have gotten in through its billing application at manage.opsshield[.]com and logged in to a customer account they had registered.
  • mSecure Urges Customers to Change their Passwords — Password manager mSecure has warned customers to change their passwords, reset two-factor authentication, and potentially remove their passkeys after detecting suspicious activity, but it has not explained what happened or whether anyone's secrets were exposed. "mSeven Software ('mSeven') recently learned of suspicious activity associated with the mSecure password management application," the company said. "In response, mSeven quickly launched an investigation, took steps to mitigate the issue, and engaged external cybersecurity experts to assist." However, the company has yet to answer what the suspicious activity involved, when it occurred, or whether attackers accessed customer information. The lack of specifics has understandably riled up customers, with one user on Reddit stating "their silence on this is mind-bending." In December 2025, Germany's cyber agency BSI found that mSecure's maker could, in theory, access the data users store in it.

‎️‍🔥 Trending CVEs

Bugs drop weekly, and the gap between a patch and an exploit is shrinking fast. These are the heavy hitters for the week: high-severity, widely used, or already being poked at in the wild.

Check the list, patch what you have, and hit the ones marked urgent first — CVE-2026-16305, CVE-2026-16306 (INFINITT PACS), CVE-2026-13684, CVE-2026-13639, CVE-2026-13673, CVE-2026-6205 (Synology DSM), CVE-2026-58868, CVE-2026-58882 (Google Android), GHSA-f3w6-w445-fwh9 (Ruby on Rails), CVE-2026-102703, CVE-2026-102704 (Xen), CVE-2026-109518 (Debian apt), CVE-2026-98432, CVE-2026-121639, CVE-2026-121638, CVE-2026-121640 (WatchGuard), CVE-2026-76506 (Cisco), CVE-2026-119741 (rsync), CVE-2026-121156, CVE-2026-121229, CVE-2026-121246, CVE-2026-121035, CVE-2026-121247, CVE-2026-121203, CVE-2026-121126 (Google Chrome), CVE-2026-98432 (Veeam), CVE-2026-83844 (Microsoft Paint), CVE-2026-19868 (SonicWall SonicOS), CVE-2026-123158 (OpenSSH), and multiple vulnerabilities in the BaseChat Android app version 9.8.1.

🎥 Cybersecurity Webinars

  • Your SOC Has an Identity Blind Spot — Here's How Attackers Exploit It and How to Close It → Your SOC may be tracking threats, but is it missing the identities behind them? As attackers increasingly exploit human, machine, and AI identities, traditional security tools often lack the context needed to detect and contain threats quickly. Join this free webinar to learn how connecting identity security with SOC operations can expose hidden risks, reveal attack blast radius, and accelerate incident response.
  • Your GitHub Actions May Still Be Vulnerable — Even With SHA Pinning. Here's Why → Think your GitHub Actions are secure because you use SHA pinning? Think again. Attackers can exploit hidden weaknesses in CI/CD workflows, even when standard security measures are in place. Join this expert-led webinar to discover how these attacks work, why SHA pinning alone isn't enough, and what you can do to protect your software supply chain.

📰 Around the Cyber World

  • The Russian-speaking ransomware-as-a-service (RaaS) operation known as Qilin (aka Agenda) has recorded 179 publicly reported attacks in 2024, and more than 1,000 claimed victims in 2025. This year alone, it has claimed more than 900 victims, making it one of the most active ransomware groups. "Affiliates commonly gain access through phishing, stolen credentials, vulnerable internet-facing systems and remote-management tools," Acronis said. "Qilin uses a flexible ransomware platform that allows affiliates to tailor attacks to the victim environment, including the encryption of local files, network shares and virtual machine infrastructure." One notable Qilin affiliate is Securotrop, which continues to operate within the Qilin affiliate network, while maintaining an independent channel for publishing stolen victim data.
  • Exposed Dixell/Copeland XWEB PRO refrigeration controllers are being turned into abuse infrastructure, according to SecurityScorecard, which uncovered a suspected SMTP botnet that includes confirmed refrigeration controllers. Attackers are said to be using compromised Dixell/Copeland XWEB PRO refrigeration controllers as proxy exits and spam senders. "The SMTP cluster consists of nine IP addresses, three of them confirmed XWEB controllers," Security Scorecard said. "Of 1,041 targets, 508 were contacted by at least two nodes. The three most active nodes had approximately 47% of their target lists in common, the report’s strongest signal of coordination."
  • A targeted Browser-in-the-Middle (BitM) phishing operation dubbed PhantomDOM is using custom DOM-mirroring to hijack Microsoft 365 sessions. "The attack began with a SharePoint-themed PDF distributed from an apparently legitimate sender and progressed through redirects and browser checks before presenting Microsoft authentication inside an attacker-controlled remote browser," ZeroBEC said. "The victim saw a familiar sign-in experience. The attacker controlled the browser in which that experience actually ran." According to the email security company, PhantomDOM goes beyond cloned login pages and conventional reverse-proxy phishing. "Its client reconstructs the remote DOM, forwards keyboard and clipboard interactions over WebSocket, survives connection interruptions and supports live operator control," it added.
  • According to a report from the non-profit AI Alignment Foundation, AI agents assigned a sandboxed coding task to fix a broken pricing service "shared a private token and ran untrusted code in exchange for help from an agent forum." In an experiment tested against nine models, GPT-6.1-Sol refused every swarm request in 50 of 50 trials, while Gemini 3.8 Flash and Claude Sonnet 5.5 trials were cut short by their providers' content filters.
  • A zero-day vulnerability has been disclosed in CPython that could enable bad actors to breach AI hosting platforms. "A memory-safety flaw in the CPython interpreter allows attackers to escape a code sandbox and execute code hidden in a specially crafted model," RunSybil said. "By exploiting this vulnerability, attackers could gain a foothold inside servers responsible for processing millions of user requests. They also could strike directly at the underlying cloud infrastructure hosting those workloads." The findings build upon a previous out-of-bounds read in CPython that could result in a sandbox escape. The issue has been fixed and backported to 3.13, 3.14, and 3.15 branches.
  • The U.S. Treasury's Financial Crimes Enforcement Network (FinCEN) has issued an order effectively cutting off MEXC Global's access to the U.S. financial system under Operation Economic Outcast. "MEXC Global is a convertible virtual currency exchanger that has facilitated at least $16 billion in illicit transactions connected to Iranian, North Korean, and Russian sanctions evasion, as well as cybercrime, including by transacting directly with sanctioned actors," FinCEN said.
  • A new study of 25,964 U.S. government-related domains has found 43 whose DNS records referenced either mistyped, expired, or otherwise repurposed domains. In one case, a misspelled domain's SPF configuration ("amzonses[.]com" instead of "amazonses[.]com") authorized at least 32,066 unique IP addresses to send email on behalf of a U.S. county. "These external dependencies authorize third-party senders, route incoming mail, provide DNS delegation, and receive security telemetry," SH Consulting said. "The government domains themselves can remain registered and be considered protected, because there are no signs to suggest anything is wrong." SH Consulting said it defensively registered 17 of these dangling DNS dependencies to prevent abuse.
  • Abraham Teklu Lemma, 53, of Maryland and a former information technology contractor at the National Reconnaissance Office, pleaded guilty to conspiring to commit espionage on behalf of the government of the Federal Democratic Republic of Ethiopia. Lemma pleaded guilty to conspiracy to transmit national defense information to a foreign government from 2021 until his arrest in August 2023 and has agreed to a prison term between 120 and 262 months. "He exploited his IT administrator access to remove classified national defense information, including Top Secret information, from a secure facility and transmitted it to Ethiopian government officials hoping they would use it to target and kill paramilitary fighters in a regional conflict," said Assistant Attorney General for National Security John A. Eisenberg.
  • Huntress has warned of a "couple waves of activity across multiple organizations involving GeoVision camera software," pointing to broad exploitation of the platform to deliver malware. The activity originates from the IP addresses 45.32.117[.]34 and 156.246.94[.]183.
  • A single AI-augmented threat actor (AAT) has been observed using a mesh of 12 AI agents called BOSSAI to conduct persistent campaigns in several countries. The mesh consists of combining HexStrike AI, Hermes, CyberStrikeAI, and HalberdStrike, alongside Grok, OpenClaw, and Claude Code, with some acting as infrastructure builders and maintainers, while others scan for vulnerabilities and attack. The findings once again show how a lone actor can mount offensive operations at scale. "Using the BOSSAI mesh, the operator targeted hundreds of organizations spanning government emergency services, banks and lenders, universities, military systems, phone directories, e-commerce platforms, and gambling sites in eleven countries," Acronis said. "It's unclear if the attacker has any specific affiliation or goal beyond compromising as many organizations as possible, presumably to monetize the activity." The threat actor is believed to be a single individual based in Hualien City, Taiwan.
  • Truffle Security has launched the Secrets Revocation Program, a free initiative that helps API key issuers revoke 1.4 million secrets that have been confirmed to be live and leaked on GitHub, Docker Hub, npm, Hugging Face, and others.
  • Gnosis Pay said it detected unauthorized access to the system powering its Gnosis Pay-branded cards on November 3, 2026, leading to the exposure of customer information. "The data breach was limited to the system powering Gnosis Pay-branded cards, which was already scheduled for retirement on 20 December 2026," it said. "We have increased our monitoring of card activity and wallets to detect fraud or attempts to access user funds. We have also implemented an extra verification step (3D Secure) and made it mandatory for all online card payments. These measures will stay in place until the B2C system is fully retired as planned on 20 December 2026." The company said it directly notified users about what information was accessed from their account, but did not reveal the number of customers impacted.
  • The U.S. Department of the Treasury's Office of Foreign Assets Control (OFAC) sanctioned four individuals and 41 entities that are tied to scam compounds in Cambodia, Madagascar, and other countries across Southeast Asia and Africa. The sanctioned parties are said to have supported the business network of Prince Group. "Cyber scam syndicates continue to steal billions of dollars from American victims while relying on sophisticated international business networks to launder their illicit proceeds," said Secretary of the Treasury Scott Bessent. "The newly designated individuals and entities have helped sustain Prince Group TCO’s illicit global operations after the October 2025 and June 2026 designations by managing offshore corporate structures, concealing beneficial ownership, facilitating commercial activities, and providing administrative and financial services to senior Prince Group TCO executives."
  • The U.S. Treasury also sanctioned Chui Kok Wa for his role as the leader of a scam compound in Madagascar that was dismantled earlier this year. Late last month, Wa was charged with conspiracy to commit wire fraud, as the leader of the NFT investment scam. "In the scheme, scammers posed as beautiful women who met victims on dating websites, eventually enlisting them to connect their cryptocurrency wallets to fraudulent websites associated with the NFT investments," the Justice Department said. "Once connected, the scammers willed the victims to continue to fund their cryptocurrency wallets, and then surreptitiously pulled money from the victims’ wallets without their knowledge." Wa's phones also allegedly contained employment contracts, detailing overnight work schedules in Madagascar and providing employees with bonus payments tied to money stolen, as well as scripts or guides for what scammers should say to victims and a roster containing employees' names, passport information, salary, hours, disciplinary actions taken against them, along with a list of cryptocurrency wallet addresses for the employees.
  • Vercel has launched Security Review, a new capability in Vercel Agent that scans for vulnerabilities on every push to a team's connected GitHub repositories. "Findings appear as comments on pull requests, are listed in the Security dashboard, and are available via CLI," Vercel said. "With your permission, Vercel Agent can also validate and push fixes for findings." In tandem, Vercel said it's starting the rollout of Device Bound Session Credentials (DBSC) for vercel[.]com to make it harder for stealer malware to siphon session cookies from a device. Google rolled out DBSC support in Chrome earlier this April.
  • Fortra has revealed that attackers are creating convincing travel-booking pages that imitate trusted rental platforms. "The fake sites use familiar branding, realistic property listings, reservation details, and urgent messages to persuade travelers to provide sensitive data such as credit card information, usernames and passwords, and more," Fortra said.
  • Patrick Steven Yaroch, 37, has pleaded guilty today to wire fraud and money laundering related to using his access as an FBI agent to steal cryptocurrency. "From 2017 through early 2025, Patrick Steven Yaroch, 37, worked at the FBI Boston Division on an investigative squad focused on an adversarial nation-state," the Justice Department said. "From February 2025 to July 31, 2026, Yaroch worked in the FBI's Counterintelligence and Espionage Division, with access to FBI systems that contained cryptocurrency credentials that the FBI had collected as part of its investigations. Beginning no later than December 2024, Yaroch used his position to steal cryptocurrency from wallets controlled by the subjects of various other investigations or by adversarial nation-state actors, and from at least one wallet the FBI created to use in an operation. Throughout his wire fraud scheme, Yaroch conducted approximately 100 fraudulent transfers using credentials related to 35 separate FBI investigations. He illicitly gained approximately $2,474,380.66 in fraudulent proceeds." The stolen funds were used to pay off his debts and finance a new life abroad, even asking ChatGPT how to maximize profit from investments and where to live in the European Union. Yaroch will be sentenced in March 2027.
  • DigiCert said it identified an event involving unauthorized access to one of its business systems, leading to exposure of names and email addresses. In some cases, driver's licenses, passports, utility bills, and other documents containing a name and address that its customers provided as proof were also compromised. The incident has been traced back to a February 2025 change that moved the internal business system to a different network segment, causing it to be opened to the public internet for more than 16 months. Unknown attackers abused a self-registration feature in the system's account manager to create a read-only account that had access to archived data between June 27 and July 2, 2026. Although DigiCert blocked the unauthorized account on July 2, it subsequently determined in October that the account was used to access archived customer contact information, including names, email addresses, phone numbers, and business addresses.
  • OpenAI announced 2 that it is increasing payouts in its Security Bug Bounty program. The objective is to get the broader research community hunting for flaws that its own testing may have missed. "A critical vulnerability in a core product such as ChatGPT, Codex, or the API Platform will now earn up to $30,000," OpenAI said. "Exceptional critical findings on those targets remain eligible for up to $100,000, and now up to $172,000 with bonuses."
  • Three people accused of using AI to impersonate corporate executives and attorneys to plunder about $129 million have been indicted on charges of wire fraud and aggravated identity theft. Jacob Soall, 41, Sharon Hazan, 54, and Guy Sheetrit, 42, targeted thousands of companies and attorneys at major law firms in order to trick employees into sending large payments to bank accounts under their control between 2024 and 2026, according to the Justice Department. Soall and Hazan were arrested in Spain in June and August 2026, respectively, while Sheetrit was arrested in the U.K. in September 2026.
  • A fake download campaign is targeting users searching for cracked commercial software, free games, activators, plugins, and unofficial utilities. The campaign uses trojanized Inno Setup-style installers hosted on bogus sites to distribute multiple payloads. "We confirmed three downstream monetization branches that transformed affected devices into monetized assets, including by routing third-party internet traffic through the device [WorldProxyPool], enrolling it in a distributed-computing platform [CharityEngine and BOINC], or installing additional utility-style software [AW Manager or Windows Manager], often without users' informed knowledge or consent," Microsoft said. "These products and components may have legitimate uses, but their silent installation through deceptive software bundles without informed user consent introduces security and privacy risks."
  • A Chinese-language exploitation framework called Greeter has targeted Flowise honeypots with thousands of chat messages reading only "hello" while weaponizing an old code injection flaw (CVE-2024-58351) to execute malicious instructions. The framework conducted system discovery, extracted environment variables, probed cloud metadata services, searched for SSH keys and other credentials, tried to set up persistence, and ran quick checks to determine whether the host could run payloads from memory. Era Security said it counted 4,372 Flowise instances exposed online, out of which 703 (21.5%) had no authentication enabled. "It reveals a new exploitation framework designed to turn exposed AI applications into entry points for code execution, credential discovery, and potentially broader cloud compromise," Era Security said. "The framework’s most consequential feature was its ephemeral, per-request execution model. Attack instructions were supplied through overrideConfig.javascriptFunction, while stored user messages contained only 'hello.' The malicious function could change with each request without altering the saved chatflow, leaving an incomplete picture for defenders inspecting workflow definitions or chat history alone."
  • A threat actor has been abusing fake "suspended account" notices to hide phishing content from users revisiting its lookalike pages masquerading as business banking and treasury logins. The campaign, active since May 2026, has been relying on more than 300 fake domains, including 248 impersonating 189 U.S. financial institutions. The first domains were registered in late 2025, but most of them appeared between July and September 2026. "What ties them together is one mechanism: the kit remembers every visitor’s IP address, so the first visit gets a bank login page, and any return visit gets what looks like a closed hosting account. We call this cluster the 'Suspended' infrastructure," KELA said. "Most domains follow the same recipe, [keyword]-[bank].com, with keywords such as secure, disable, protect and cancel, which makes the cluster findable in newly registered domain feeds."
  • Meta said it paid nearly $1.2 million in bug bounties to researchers who found and responsibly disclosed issues in its Muse AI assistant. The bug bounty program went public in September 2026. "The largest single award was paid out four months before launch for a bug that allowed a researcher to get access to conversations and tokens in pre-release VMs used by employees and engineers testing the product," Meta said. "An authentication check treated a header added by a local HTTPS proxy as proof that a request came from a trusted source. During a system migration, the environment gained a second proxy layer. That meant requests from outside could carry the trusted header too. A researcher found this and demonstrated the exploit." Meta paid a $300,000 bounty for this report.
  • Chinese nation-state threat activity declined by 41.4% in the six months from April to September 2026, according to a new study by Trellix. The change is "a shift in operational focus, we assess, rather than reduced intent, and one that warrants vigilance rather than reassurance," it added.
  • QNAP is urging users to update Plex Media Server on their NAS instances to the latest version available in the QNAP App Center following reports of active exploitation of a set of vulnerabilities known as Plex2Shell. "QNAP has received reports from some users that Plex Media Server on their NAS appears to have been compromised through these vulnerabilities," it said. "The QNAP Technical Support team is assisting affected users and has confirmed that no data loss has occurred."
  • MetaMask has disclosed that the security incident it identified on September 28, 2026, resulted in unauthorized access to part of its infrastructure, and that it took steps to contain the incident and secure affected systems. "We have identified no indication that MetaMask wallets or our wallet infrastructure were compromised as a result of this incident," it said. "We have not identified evidence that the incident enabled unauthorized access to or withdrawal of customers' staked principal. However, a limited amount of execution-layer staking rewards was diverted during the incident." The attacker is said to have briefly altered the addresses used to receive execution-layer staking rewards for certain validators, diverting approximately 0.385 ETH in rewards. "These rewards are separate from customers' staked ETH," MetaMask added. "We have found no evidence that customers’ staked principal or withdrawal keys were compromised, and the affected systems have been secured."
  • Infected security-themed GitHub projects are being used to target cybersecurity professionals to deliver backdoors and infostealer malware. According to Doctor Web, more than 2,000 PCs have been affected. The malicious code is embedded in Visual Studio project files, Python scripts, and Go source files. Once launched, the malware establishes persistence on the infected host, escalates privileges, disables security and recovery features, and deploys additional payloads, including AsyncRAT, a clipper malware, and an information stealer. The malware also attempts to remove ESET, McAfee, and Malwarebytes antivirus tools from the host and interferes with Windows backups. "The attackers behind these compromised development projects target blockchain game enthusiasts and (most intriguingly) information security professionals," the Russian cybersecurity company said. "The first infected repositories emerged two years ago. The early uploads targeted crypto wallet users – back then attackers used repositories containing Visual Studio projects related to blockchain games, game bots and cheating."
  • Security researcher Scott Helme has revealed that about 15,579 websites are currently infected with malicious JavaScript delivering credit card skimmers, ClickFix lures, iOS exploitation kits like Coruna and DarkSword, and malicious redirects. These websites receive more than 135 million visits every month.
  • A new report from Layer3 Intel has found that residential proxy traffic has exited through the White House network (AS2650) 236 times over a 30-day period between October 5 and November 3, 2026, with 28 separate residential proxy services able to route traffic through six of its addresses. "Most of the activity happens in the evening, Eastern time: about half of it falls between 5 p.m. and midnight, and almost none happens in the early morning," Layer3 Intel said. "That pattern suggests a person rather than a public guest Wi-Fi network: someone regularly on the White House network late into the evening, whose device is infected with a proxy SDK. Our data shows the exits, not the device or the person behind them." In a post shared on X, Synthient said "several White House staffers are running a Windows 11 machine with InfaticaSDK installed," adding it found "a number of Windows 10 and Windows 11 devices beaconing to known proxy providers like Geonode, Infatica, and Mellowtel." The root cause is believed to be Rave[.]io, a shared streaming app that bundles 12 proxy SDKs into the platform. Rave allows users to watch content from YouTube, Netflix, and Disney+ with friends and runs on Mac, iPhone, Android, and Windows.
  • A set of five vulnerabilities has been disclosed in Reachy Mini, an open-source, expressive companion robot from Pollen Robotics and Hugging Face, that, when chained together, can allow an attacker to "execute attacker code, escalate to a persistent root via the robot’s passwordless sudo, and ultimately gain control of the device's motor," JFrog said. "A second variant of the attack works through the browser, where the operator visits a malicious web page, which silently compromises the robot."
  • A phishing campaign built around fake registration pages for OpenAI, SpaceX and Anthropic events is luring marketing employees with rewards like "3 months of ChatGPT Pro" or "3 months of Grok Heavy" to get them to sign in with their work accounts. "This campaign uses them in email-delivered invitations that lead to AitM and device code phishing, expanding the use of AI-themed lures across various payload types," Push Security said. "Employees want access to the latest AI tools, making them excellent bait for attacks." The Microsoft option launches a device code phishing flow run through the Kali365 phishing-as-a-service platform, while clicking "Continue with Google" opens a VoidProxy reverse proxy of Google's sign-in page. It is unclear how the attackers initially distribute the phishing links. The kits used to build and deploy the fake event invite lure pages as ZoomMock and MSDRoot. Similar campaigns have been reported by ANY.RUN and Cofense in recent months.
  • A U.S. school estate was compromised by the 3AM ransomware group as part of a hybrid human-AI operation, according to Bitdefender. The exact initial access vector used is unknown, but the first recorded activity started on September 10, 2026. "Some parts show a human operator at the keyboard while others behave like an agentic loop, a language model reading each result and retrying with different commands," Bitdefender said. "With the exception of the encryptor itself, the whole operation was built on legitimate, built-in tools, which is standard for ransomware operations. What is different is how the attacker behaved, and several things point to an agentic loop, a program that feeds each result back to a model and runs what comes back. The retries behave like a loop too."

Conclusion

The strange part is how many of these attacks start with something small. A setting nobody checked, an update nobody questioned, or a system left online longer than it should have been. Add a little patience from the attackers, and suddenly a minor mistake becomes a much bigger problem. Not every attack needs a clever trick.

That's it for this week's roundup. Some of these stories will fade, while others may get worse as more details come out. Either way, there's enough here to keep security teams busy. Check what applies to your systems, fix what you can, and we'll be back next week with whatever turns up next.



from The Hacker News https://ift.tt/n5YuaAs
via IFTTT