TIGR Threat Watch

Threat Watch Feed

🚩 – IOCs Added

The red flag indicates that Indicators of Compromise (IOCs) have been added to SRA’s Threat Feed used by CyberSOC clients. Articles may not be flagged if IOCs are not available at the time or are not applicable to the article.

Eight eMudhra Intermediate CA Private Keys Compromised Through Insufficient Randomness

Unit 42 published an advisory on October 22, 2026 on the compromise of eight intermediate certificate authority private keys belonging to Indian certificate authority eMudhra Limited. The keys were generated with insufficient randomness during the certificate generation process, a critical cryptographic defect that allows a third party to derive the private keys directly from the publicly available certificates. No intrusion into eMudhra was required, as the weakness is in the key material itself and is exploitable by anyone who obtains the public certificates.

With a derived private key, an attacker can sign unauthorized public TLS certificates for any domain and use them to conduct meddler-in-the-middle traffic interception, impersonation, or session hijacking against targeted domains. eMudhra has revoked the eight affected certificates, and major browser and operating system vendors have moved to revoke or untrust these intermediate CAs. Unit 42’s guidance focuses on discovery and internal exposure assessment, technical containment and reissuance, active threat hunting across network and authentication telemetry, and longer-term PKI governance including Certificate Transparency monitoring and CAA enforcement. The advisory does not state when the defect was introduced, how long the certificates were in circulation, or whether any unauthorized certificates were observed in the wild.

Impact: A derived intermediate CA key allows an attacker to mint a certificate that chains to a publicly trusted root, which means a forged certificate for any domain would validate silently in a browser or client that has not yet applied a distrust update. The interception window is therefore defined by trust store update latency rather than by anything the targeted organization controls, and systems that fall outside normal update cycles are the exposure that matters most. Embedded trust anchors are the hard part: Java keystores, Python certifi bundles, Docker base images, mobile application bundles, appliances, and IoT devices often carry static certificate stores that no MDM push will reach, and those clients will continue accepting forged chains until each is individually updated. Any organization holding certificates issued under the affected intermediates also faces operational disruption, since those certificates are now revoked and the services relying on them will fail validation until reissued.

Recommendation:

  • Inventory all public-facing services, web applications, API endpoints, VPN gateways, and internal infrastructure for active TLS certificates chaining to eMudhra intermediate CAs.

  • Revoke and reissue any certificate issued under the affected intermediates through an alternative fully trusted CA.

  • Push updated root and intermediate trust stores through MDM to all endpoints, servers, and container images to explicitly distrust the affected intermediates.

  • Search custom and embedded trust stores, including /etc/ssl/certs, Java keystores, Python certifi bundles, Docker base images, and mobile application bundles, for eMudhra roots or intermediates.

  • Audit code repositories, build pipelines, containers, and deployment scripts for bundled eMudhra certificates or hard-coded trust anchors.

  • Hunt network, proxy, and DNS logs for connections to unknown external addresses presenting eMudhra-signed certificates.

  • Investigate unexplained spikes in TLS handshake failures, certificate validation errors, or untrusted issuer warnings, which may indicate interception or proxy insertion.

  • Review authentication logs for SSO, VPN, and cloud portals around the compromise window for signs of intercepted or replayed sessions.

  • Monitor Certificate Transparency logs for unauthorized certificates issued for your registered domains.

🚩 Stadia RAT Reuses StealC Code Four Months After Europol Takedown

Varonis Threat Labs has analyzed Stadia, a remote access trojan that shares code with StealC, the infostealer Europol disrupted in June as part of Operation Endgame. Varonis links the seller to StealC through code overlap and a seller alias. The seller relaunched on October 16 with a subscription web panel priced from $300 to $900 a month. The top tier includes hidden remote desktop, a remote command shell, a file explorer, a process manager, and a loader, with StealC’s stealer as one module. Former StealC customers are offered a free month on that tier. A 26 KB Chromium App-Bound Encryption helper in the sample is byte for byte identical to one in StealC 3.5 builds. The remote access capabilities are documented in the seller’s listing and decrypted strings, but Varonis has not yet observed them operating on a victim, as its own dynamic run failed to execute the sample.

Once installed, the agent hides in a randomized folder under C:\ProgramData\ with file names that imitate legitimate updaters. It persists through a hidden scheduled task and, when elevated, adds a Windows Defender exclusion for its folder. It sends traffic to hard-coded IP addresses over plain HTTP, encoding the payload so it doesn’t match the JSON content type it declares. Varonis reports the agent injects code into suspended browser processes to steal saved credentials and session cookies. The article documents no confirmed victim infections, and the several-hundred-host dashboard figures come from the seller’s demo screenshots and remain unverified.

Impact: Stadia would give an operator hands-on control of an infected Windows system if its advertised modules work as described, including desktop viewing and control, command execution, file transfer, and payload deployment. The stealer adds saved passwords, session tokens, and cryptocurrency wallet data, which together create a real risk of account takeover. Pricing from $300 to $900 a month, including a Team tier, could put the tool in the hands of more operators. Varonis has not observed these modules on a victim, so the actual scale and severity remain unconfirmed.

Recommendations:

  • Block unsigned executables in user-writable locations. Use application control such as AppLocker or WDAC to stop unsigned executables from running out of C:\ProgramData\ and other user-writable paths.

  • Alert on the scheduled task pattern. Deploy Varonis’s Sigma rule in alert mode to flag hidden scheduled tasks that repeat every 15 minutes and run from C:\ProgramData. Also review task creation outside schtasks.exe, since the implant registers tasks through the COM API.

  • Alert on browser code injection. Flag unsigned processes that write code into Chrome, Edge, or Brave processes, which matches the credential theft technique described.

  • Respond to suspected infection by cutting off stolen sessions. Revoke active browser sessions and tokens, and rotate saved passwords. Replace cryptocurrency wallets if seed phrases were stored on affected hosts.

PHP Discloses Unpatched Code Execution Issue Days After Emergency PHP2Shell Fixes

PHP published a short informational advisory on October 23, 2026 disclosing CVE-2026-115560, a separate code execution issue affecting a narrow set of web application configurations. The project assesses the risk as unlikely and is not issuing an emergency release, instead recommending that administrators disable the session upload progress feature until a fix ships in the next routine bugfix release. PHP has not stated which versions are affected, which release will contain the fix, a severity score, or whether the issue shares a root cause with the earlier PHP2Shell flaws.

Exposure requires a specific and uncommon configuration sequence: the application sets session.serialize_handler to php_binary or php_serialize in configuration, then changes that option to php at runtime via ini_set(), and makes that change before calling session_start(), with session upload progress still enabled. An application that never changes the serialize handler at runtime is not exposed through this path even with the feature enabled. The recommended mitigation is a single setting, session.upload_progress.enabled=0, which is the same mitigation PHP already listed in its October 21 advisory for CVE-2026-109619. Organizations that applied it then and left it in place need no further action. The disclosure follows PHP’s October 21 emergency release addressing the critical PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619, which allowed unauthenticated code execution and were patched in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.

Impact: The direct exposure is limited, since the required configuration pattern is unusual and PHP itself characterizes it as unlikely in practice, and the one-line mitigation costs little to apply. The more consequential point is the context: the critical PHP2Shell flaws disclosed two days earlier are unauthenticated remote code execution and are already being exploited in the wild, so any organization only now reviewing its PHP posture because of this advisory has a more urgent problem to address first. Session upload progress is enabled by default, which means the mitigation requires a deliberate configuration change rather than relying on a safe default.

Recommendation:

  • Confirm that the October 21 emergency patches are applied, upgrading to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, since the exploited PHP2Shell flaws are the higher priority.

  • Set session.upload_progress.enabled=0 across PHP deployments until the next routine bugfix release, which also covers the CVE-2026-109619 mitigation.

  • Verify the setting remains in place on systems where it was applied on October 21, as no further action is needed there.

  • Identify applications that set session.serialize_handler to php_binary or php_serialize and change it at runtime with ini_set() before session_start(), as those are the configurations exposed by this issue.

  • Confirm whether any application genuinely requires session upload progress before leaving it enabled, since it is on by default and tracks file upload progress only.

  • Monitor http://php.net advisories and the next routine PHP release for the full CVE-2026-115560 advisory, affected version list, and fix.

ESET Uncovers MythicRatatoskr, a Yggdrasil-based Backdoor Deployed By Russia-Aligned UAC-0099 in an Intrusion that Culminated in a Destructive Sandworm Attack Against a Ukrainian Grain Logistics Company.

On October 22, 2026, ESET Research disclosed MythicRatatoskr, a previously undocumented Go-based backdoor identified during a coordinated intrusion involving Russia-aligned threat groups UAC-0099 and Sandworm. On July 16, 2025, UAC-0099 gained initial access to a Ukrainian grain logistics company through a spearphishing email containing a malicious attachment. The infection chain involved a scheduled task named pdfopentask, which executed PowerShell from %TEMP%\temporarydoc.txt, followed by the MATCHBOIL downloader and MATCHWOK backdoor. On July 17, attackers deployed MythicRatatoskr and subsequently distributed additional samples to other systems using OpenSSH SFTP. ESET assesses with high confidence that UAC-0099 handed off access to Sandworm, which conducted a destructive data-wiping attack on September 17, 2025, using SDelete deployed through Active Directory Group Policy. However, researchers could not determine whether UAC-0099 or Sandworm primarily operated MythicRatatoskr.

MythicRatatoskr communicates with its command-and-control (C2) server through Yggdrasil, a decentralized mesh network providing end-to-end-protected IPv6 communications. The malware uses a user-space networking implementation based on yggstack, connects to three randomly selected public peers from an embedded list of 32, and communicates with its C2 server at 201:b479:2771:8df4:b5eb:d007:63b0:2838 over HTTPS on port 443. Its capabilities include remote command execution through cmd.exe, file transfer, screenshot capture, system reconnaissance, and reverse SOCKS5 proxying. Persistence is established through a Windows service named ieupdate, while encrypted configuration files are stored at locations such as C:\Windows\Temp\.updatecache. Some samples introduce a 10-minute startup delay to reduce immediate detection. Researchers also identified a separate Go-based SOCKS5 server listening on 127.0.0.1:33690, likely deployed through MythicRatatoskr, and found artifacts suggesting a possible Linux variant, although its existence remains unconfirmed.

Impact: The intrusion demonstrates how coordinated threat actors can combine initial access, persistent remote control, internal network access, and destructive operations against strategically important organizations. MythicRatatoskr enables attackers to execute commands, collect system information, capture screenshots, transfer files, and route traffic through compromised environments. Its use of Yggdrasil complicates network-based detection because the C2 server resides within an encrypted IPv6 mesh rather than being contacted directly over conventional internet infrastructure. The confirmed deployment of SDelete through Active Directory Group Policy demonstrates the potential for widespread data destruction after an attacker obtains sufficient administrative control. While ESET documented this activity against a Ukrainian grain logistics company, the report does not establish broader MythicRatatoskr deployment across other organizations.

Recommendation:

  • Strengthen email security controls to identify malicious spearphishing attachments and investigate suspicious document-triggered PowerShell execution, particularly scheduled tasks such as pdfopentask launching scripts from %TEMP%.

  • Hunt for MATCHBOIL and MATCHWOK activity, including the UpdateMonitor registry value under HKCU\Software\Microsoft\Windows\CurrentVersion\Run and communications with uztickets[.]com or egyptanimals[.]com/animals/photoalbum.

  • Monitor Windows service creation and execution for unauthorized services named ieupdate, particularly those launching executables such as ieupdate.exe, updater.exe, WindowsDefenderSvc.exe, or krbtman.exe.

  • Inspect suspicious executable locations, including C:\Windows\System32\, %LOCALAPPDATA%\Microsoft\OneDrive\, and %LOCALAPPDATA%\Internet Explorer\, for unauthorized binaries matching the identified MythicRatatoskr artifacts.

  • Hunt for encrypted configuration files at C:\Windows\Temp\.updatecache, C:\Windows\System32\.updatecache, and %LOCALAPPDATA%\Temp\.crond, correlating file creation with suspicious service execution.

  • Monitor outbound connections to Yggdrasil public peers, particularly unusual TLS, TCP, or QUIC traffic associated with the peer infrastructure documented by ESET. Investigate unauthorized use of Yggdrasil networking components.

  • Investigate communications involving the identified Yggdrasil C2 address 201:b479:2771:8df4:b5eb:d007:63b0:2838, including HTTPS on port 443 and reverse proxy activity on port 8080 where mesh-network telemetry is available.

  • Hunt for unauthorized SOCKS5 proxy services, including processes listening on 127.0.0.1:33690, and investigate suspicious network tunneling, port forwarding, and internal proxy activity.

  • Monitor Active Directory Group Policy modifications for unauthorized software deployment, suspicious administrative activity, and attempts to distribute destructive utilities such as SDelete across domain-joined systems.

  • Validate backup and recovery protections by restricting backup administration, maintaining isolated or immutable recovery copies, and testing restoration procedures against destructive attacks involving centralized administrative deployment.

Group-IB Identifies SiriusQT, a Windows RAT with Hidden Desktop Control, Credential Theft, and Persistence Capabilities used in Multiple Malicious Campaigns.

Group-IB disclosed an analysis of SiriusQT, a Windows remote access trojan (RAT) distributed through a malware-as-a-service (MaaS) model. The malware has been advertised on underground forums, with at least 30 users purchasing valid licenses. Researchers identified more than 280 SiriusQT client samples associated with different campaigns, including activity targeting the United Kingdom, Germany, France, Spain, Italy, and the Netherlands. The malware provides attackers with remote access, credential theft, keylogging, cryptocurrency wallet collection, and browser interaction capabilities.

SiriusQT uses Hidden Virtual Network Computing (HVNC) to provide attackers with a concealed desktop session, allowing interaction with applications without displaying activity on the victim’s normal desktop. The malware also supports process injection, anti-analysis checks, encrypted command-and-control (C2) communications, and multiple persistence mechanisms, including registry Run keys, scheduled tasks, Startup folder shortcuts, and logon scripts. Additional persistence options can modify the Windows BootExecute registry value or the Default User profile. Group-IB confirmed malicious campaigns involving SiriusQT samples and identified instances where the malware was delivered as a final-stage payload through the UpCrypter loader. However, the analyzed standalone client exhibited high detection rates, potentially limiting its effectiveness without additional evasion techniques.

Impact: SiriusQT poses a risk to organizations through unauthorized remote access, credential compromise, and sensitive information theft. Its HVNC functionality enables attackers to interact with browsers and applications through hidden desktop sessions, potentially facilitating fraudulent activity without obvious user-visible indicators. Credential theft, keylogging, and cryptocurrency wallet collection can expose corporate accounts and financial assets. Multiple persistence mechanisms increase the likelihood of continued unauthorized access, while encrypted C2 communications and process injection may complicate detection and investigation.

Recommendation:

  • Organizations should review Group-IB’s research and assess their exposure to SiriusQT and associated delivery mechanisms. Recommendations include:

  • Deploy and maintain updated endpoint detection and response (EDR) protections capable of identifying RAT activity, process injection, credential theft, and suspicious remote desktop behavior.

  • Monitor Windows registry Run keys, particularly HKCU\Software\Microsoft\Windows\CurrentVersion\Run, for unexpected entries or executables masquerading as Windows Update components.

  • Review scheduled task creation and modification events, including suspicious use of schtasks.exe and tasks named Windows Update that execute from unusual locations.

  • Monitor Startup folder shortcuts, UserInitMprLogonScript registry modifications, and unauthorized changes to the BootExecute value under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager.

  • Restrict administrative privileges and monitor unauthorized modifications to the Windows Default User profile, including C:\Users\Default\NTUSER.DAT.

  • Investigate suspicious outbound connections to unfamiliar C2 infrastructure, including indicators published by Group-IB. Review connections to cloud-hosted infrastructure when accompanied by suspicious endpoint behavior.

  • Hunt for unusual process injection activity, hidden desktop creation, and unauthorized browser automation that may indicate SiriusQT’s HVNC functionality.

  • Monitor for suspicious access to browser credential stores, cryptocurrency wallet data, and other sensitive application files.

  • Restrict execution of untrusted software and investigate suspicious loaders, packed executables, and unexpected files downloaded through email, messaging platforms, or unverified websites.

  • If SiriusQT is detected, isolate affected endpoints, investigate persistence and lateral activity, and rotate potentially compromised credentials after containment.

GitLab Releases Patches for CVSS 10.0 Unauthenticated Code Execution Flaw Affecting Self-Managed Instances Back to Version 7.0.

GitLab disclosed CVE-2026-110264, a flaw rated 10.0 on the CVSS scale affecting GitLab Community Edition and Enterprise Edition. Self-managed GitLab installations are affected on all versions before the fixed release for their branch, back to 7.0. GitLab.com is already patched, and GitLab Dedicated is covered on builds 19.3.5-internal0, 19.4.2-internal0, or later.

The flaw is an integer overflow in GitLab’s Regular Expression Compiler, the background engine that parses regular expressions in configuration files. Under conditions that GitLab has not described, an unauthenticated remote attacker could send a specially crafted regular expression and execute arbitrary code on the server. GitLab reports no evidence that the flaw has been exploited.

Impact: Exploitation requires no authentication, and GitLab has not defined the preconditions, so administrators cannot yet rule themselves out through configuration. A successful attack would give an attacker code execution on the server, which could expose the secrets, pipeline data, and repositories that GitLab instances hold. Shadowserver tracks more than 2,700 internet-exposed GitLab CE instances, though it does not indicate how many are already secured or are honeypots.

Recommendations:

  • Upgrade GitLab CE/EE self-managed instances to the fixed release for your branch: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, or 18.11.13.

  • Deploy the two GitLab-published detections, “Onigmo native worker crash” and “Org mode render error burst,” against your GitLab application logs to look for exploitation attempts.

  • If an exposed instance may have been targeted before patching, consider reviewing logs and rotating credentials and CI/CD secrets stored on the server.

Sign up here!

To receive the TIGR Threat Watch email bulletin and critical vulnerability notifications, simply complete the form below.

 

Follow on Twitter

@SRA_ThreatWatch will keep you up to date with the most recent posts on your social media feed.

Subscribe to the RSS

Just copy and add this link to your RSS app and be notified immediately when new intel is posted.

How to use RSS

Following the RSS feed is easy. RSS can be added in your Outlook desktop app, and there are many free RSS readers available for your mobile device.

To follow using Outlook:

  • In Outlook, right-click the RSS Feeds folder and choose Add a New RSS Feed.
  • In the New RSS Feed dialog box, enter the URL of the RSS Feed: https://sra.io/category/tigr/feed

(click here for detailed instructions and additional options for Outlook)

Popular mobile RSS reader apps include:

  • Feedly
  • NewsBlur
  • RSS Reader
  • Inoreader

After installing your preferred RSS reader, you will be able to add this feed by entering the URL: https://sra.io/category/tigr/feed

Threat Bulletin Archive

About TIGR Threat Watch

Our Threat Intelligence Gathering & Research (TIGR) team is focused on threat intelligence and curates a daily intelligence report, TIGR Threat Watch, with information collected from several industry intel sources. We also create and publish ad-hoc critical vulnerability notifications in case of critical and time-sensitive vulnerabilities or threats. These notifications include details and recommendations for mitigation/remediation.