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.
Check Point Confirms Active Exploitation of Gaia OS Privilege Escalation Flaw
Check Point confirmed active exploitation of CVE-2026-123039 (CVSS 7.8, High), a local privilege escalation vulnerability in Gaia OS. The Dynamic CLI service runs as root and accepted unauthenticated requests through a local socket that any local user could write to. An attacker who already has code execution on the appliance can use the flaw to gain root privileges. Check Point reported exploitation against roughly two dozen customers in its November 12 advisory.
Check Point Research documented attackers chaining this flaw with PHP2Shell. In the investigated campaign, attackers gained initial access through unpatched Mobile Access portals, then used the Gaia flaw to elevate privileges. Researchers observed persistent backdoors and, in some incidents, attackers pivoting over SSH to VMware ESXi hosts and deploying a wiper.
Impact: Check Point lists Force Firewalls, Management and Log Servers, Multi-Domain Management and Log Servers, and Maestro Orchestrator as affected. The advisory lists versions R81 through R82.20, including the end-of-support R81 and R81.10 releases. Spark Firewalls and Smart-1 Cloud are excluded. Root access can let an attacker alter appliance settings, tamper with logs, install persistence, or move into connected systems.
Recommendation:
-
Apply the fixed Jumbo Hotfix. Check Point lists these minimum builds: R82.20 Take 14, R82.10 Take 52, R82 Take 132, and R81.20 Take 174. Move R81 and R81.10 appliances to a supported release. Check internet-facing Mobile Access portals for PHP2Shell exposure and apply the separate fix.
-
Mitigate if patching must wait. Follow the vendor advisory to stop
dynamic_serverand prevent it from restarting. This disables the affected Dynamic CLI commands. After patching, verify that/tmp/dynamic_socketis owned byroot:configwith permissions set to0660. -
Hunt for activity before and after patching. Review
/var/log/dynamicCli.logacross appliances and cluster members forReceived =entries that lack the expected Clish wrapper. Correlate anomalies with portal and authentication logs, unexpected outbound SSH, and signs of persistence. A post-patchRejected connection from unauthorized uidentry records a blocked request; it does not establish successful exploitation. If you find evidence of compromise, preserve logs and investigate connected systems. Applying the fix does not remove existing backdoors.
🚩 FBI Warns of FaceStealer Scheme Using Recorded Victim Webcam Video in $400M Crypto Theft Campaign
The FBI published FLASH AC-111226-MS on November 12, 2026 alerting the cryptocurrency and web3 industry and open-source software maintainers to a North Korean social engineering scheme it calls FaceStealer. The FBI attributes the activity to North Korean state-sponsored actors known as Sapphire Sleet, UNC1069, Dangerous Password, CryptoCore, APT38, BlueNoroff, and Stardust Chollima, and reports more than $400 million in cryptocurrency stolen over the past 18 months alongside attempts to compromise the open-source software supply chain. The FBI has identified and seized over 900 victim webcam videos used to impersonate prior victims in follow-on attacks.
The scheme is self-propagating. From an already compromised victim, the actors scan for wallets and seed phrases, take over the victim’s Telegram or other encrypted communication app, access contact lists and chat histories, and secretly record the victim’s webcam. They then impersonate that victim to invite contacts to a video meeting, using Calendly or similar services to schedule and sending a typo-squatted Zoom or Teams link shortly before the meeting to limit infrastructure exposure. The link leads to an actor-controlled copycat of Zoom or Teams, where the stored webcam video of the trusted contact is played, often alongside additional videos to simulate multiple participants. The actor then messages the target claiming an audio or technical problem and directs them to click an update prompt, run a script, or paste code into a terminal, which installs a cookie harvester, keyloggers, screen capturers, and a backdoor while the target’s own webcam is recorded for the next cycle. The FBI notes the actors have begun using AI-generated deepfakes of well-known cryptocurrency and web3 figures to supplement real victim video, though the scheme still relies overwhelmingly on genuine recordings. The actors also target software maintainers, and earlier this year compromised a maintainer of a significant open-source JavaScript library receiving tens of millions of downloads per week, using that access to create malicious dependencies before the compromise was detected. Further attempts have targeted NPM maintainers and, more recently, maintainers of Rust crates.
Impact: Usual verification heuristics fail here because the invitation arrives from a genuine account belonging to a real contact, the chat history is authentic, and the face on the video call is the actual person. The compounding structure means each successful compromise supplies both a new victim and new impersonation material, so the target pool grows with every infection. Patience is a defining characteristic, with theft occurring months to over a year after initial compromise as operators copy seed phrases, monitor balances on-chain, and reconstitute wallets once funds accumulate, meaning a cleaned device does not end the exposure if recovery material was taken. Organizations are also exposed indirectly, as victims compromised on personal devices may hold corporate credentials, work files, or repository access.
Recommendation:
-
Join video meetings through the official desktop application using an invite code rather than clicking links to web versions, particularly for invitations from new or infrequent contacts.
-
Keep the webcam off until you can see, hear, and interact with the person who invited you, which creates an opportunity to verify before supplying your own video feed.
-
Never run scripts or paste code into a command line or terminal in response to an in-meeting update or troubleshooting prompt, and update the application separately instead.
-
Inspect calendar invites for meeting links, noting the actors typically omit links at scheduling and send malicious links closer to the meeting time.
-
Secure Telegram, WhatsApp, Slack, and similar apps with multifactor authentication, login alerts, and expiring messages, since account hijacking is how the lure gains credibility.
-
Keep only low-value balances in browser extension wallets, hold larger balances on a hardware device or with an exchange, and never store seed phrases or private keys on any device.
-
On suspected compromise, create a new wallet with new seed phrases on a device never used to communicate with the actors and transfer assets to it immediately.
-
Change all passwords, log off active sessions, and add multifactor authentication to communication, developer, and other sensitive accounts.
-
Notify contacts that your accounts may be hijacked and that prerecorded webcam video may be used to impersonate you, and notify employers if a work device or work files were involved.
-
For open-source maintainers, enforce phishing-resistant MFA on registry and repository accounts, require signed commits and reviewed releases, and monitor for unexpected dependency changes.
🚩 LIMINAL PANDA Deploys New GTP-U Backdoor as Enea Identifies SilentAir Signalling Actor
Enea published research on November 11, 2026 documenting ongoing 2026 activity by the China-nexus LIMINAL PANDA actor against mobile operator signalling interconnects, alongside a newly identified signalling actor it names SilentAir. Enea detected and blocked several hundred covert GTPDoor command and control communications on the GTP-C interface across multiple customer operators from Q1 2026 onward, with direct evidence of 5 to 10 infected operators and an assessment that several dozen may be infected globally across Asia, Africa, and Latin America. Observed commands covered exfiltration tunnel setup using modified SGSNemu, lateral movement via EchoBackdoor, SSH initiation, and anti-forensic activity including file deletion and timestomping. Enea also identified a new variant it calls GTPDoor v3, which operates over GTP-U rather than GTP-C, retains the earlier default XOR key, and adopts libpcap so the listener does not appear in netstat or lsof.
SilentAir is assessed with high confidence as a state-level actor and with low confidence as China-nexus. It injects SS7 and Diameter attacks from compromised nodes inside infected operators, with suspicious elements identified in at least six Asian countries targeting subscribers in a dozen more. Taiwan is the primary target, Chinese networks are conspicuously absent, and political and government VIPs were among those targeted. Unlike surveillance company activity dominated by harvesting and location tracking, SilentAir’s activity is 18.3 percent interception and 74.3 percent other, the latter largely silent SMS used to verify that malicious Update Location attacks remain in place. Enea observed 2FA codes arriving immediately after interception for some targets, and attack timing aligns with a UTC+8 working day with pauses around Chinese holidays. Links to LIMINAL PANDA are possible but unconfirmed, based on shared timing, overlapping targeting, and partial similarity to the SCTPE binary, which SilentAir’s behavior nonetheless exceeds since it responds to transactions it did not initiate.
Impact: Access to any one of the world’s 800 plus mobile operators grants reach to all the others through the trusted IPX interconnect, so a single compromised operator becomes a platform for attacking subscribers of every other network. The GTP-U variant matters because it moves the covert channel into the highest-volume traffic on that interconnect, where operators have invested least in inspection, and because GTP-U survives into 5G while GTP-C does not. On the SilentAir side the consequences reach subscribers directly, since malicious Update Location places the attacker in the delivery path for future calls and SMS, and the observed 2FA interception converts signalling access into account takeover against targets with no visibility and no available remedy. The recurring finding that operators outsource core network operations is a practical obstacle, since incomplete ownership makes sensitive investigation substantially harder.
Recommendation:
-
Deploy GTP-C and GTP-U security systems or firewalls, and ensure they share information with SS7 and Diameter firewalls rather than operating in isolation.
-
Treat the entire IPX interface as untrusted, extending analysis and filtering across all interconnect protocols including DNS and ICMP.
-
Treat GSMA recommendations as a baseline rather than an endpoint, since advanced actors specifically operate outside rote protections.
-
Extend detection logic to internal signalling interfaces, where tools such as SIGTRANslator and Cordscan are used for C2 relay and discovery.
-
Integrate signalling and IPX detections with the operator’s broader IT security program, since LIMINAL PANDA moves freely between signalling protocols and conventional access such as SSH.
-
Hunt for the published GTPDoor v3 and SCTPE samples, noting GTPDoor v3 uses libpcap and will not appear in netstat or lsof.
-
Alert on malicious Update Location activity, on nodes responding inconsistently to uninitiated transactions, and on Global Titles closely resembling legitimate network elements.
-
Alert on high-volume silent SMS, particularly midnight-concentrated bursts, and on SMS submitted through intermediate SMSCs rather than sent directly.
-
Review investigative access and visibility where core network operations are outsourced to vendors.
Actively Exploited Xen Orchestra Flaws Enable Authentication Bypass and XCP-ng Host Takeover
Vates disclosed two security vulnerabilities affecting Xen Orchestra and Xen Orchestra Appliance (XOA) that have been associated with active attacks. The critical authentication bypass, tracked as VSA-2026-062, allows unauthenticated attackers to gain administrator privileges. A second vulnerability, VSA-2026-063, involves crafted virtual machine imports that could compromise XCP-ng virtualization hosts. Vates released fixes for the authentication bypass, while the VM import vulnerability remains unpatched.
VSA-2026-062 exploits improper REST authentication token handling by submitting a crafted cookie containing an empty JSON object, allowing attackers to authenticate using an existing token. Once authenticated, attackers can retrieve reusable tokens and potentially execute arbitrary code on managed hosts. VSA-2026-063 allows users with specific VM import or network privileges to manipulate protected VM configuration fields through crafted XVA files. Active exploitation is confirmed, including abuse of the VM import path by an attacker with administrator privileges, although exploitation of that path by an unprivileged account was not established.
Impact: Successful exploitation could allow attackers to gain administrative control of Xen Orchestra, compromise managed virtual machines, and take over XCP-ng hosts with root privileges. The VM import vulnerability creates additional risk for environments where nonadministrative users retain import-related permissions. Unauthorized access through the authentication bypass may not appear in application logs, complicating detection. Organizations managing multiple virtualization hosts through Xen Orchestra could face widespread infrastructure compromise, persistent unauthorized access, and disruption to critical workloads.
Recommendation:
-
Patch VSA-2026-062 immediately. Update Xen Orchestra to at least 6.9.1 (stable) or 6.10.0 (latest), including the corresponding patched xo-server packages.
-
Mitigate VSA-2026-063. Restrict VM imports to administrators and remove unnecessary vm.import, sr/import:vm, network/action:create, and network/action:update privileges until a fix is available.
-
Restrict management access. Place Xen Orchestra behind dedicated management networks and prevent direct exposure to the public internet.
-
Monitor suspicious authentication requests. Inspect HTTP traffic for authenticationToken=j:%7B%7D or authenticationToken=j:{} and block these patterns using a WAF or reverse proxy.
-
Hunt for compromise indicators. Investigate VMs named pivot2, configurations containing hvm_serial: file, and suspicious files such as /etc/cron.d/zz-ustar* or /.ustar*.
-
Review malicious infrastructure. Investigate connections to 91.211.251[.]112:8001 and ustar3rqxgnskzgnwkgpofgtvxevm6cx3lxdbwt4mndtveqyaohid[.]onion:3333.
-
Remediate confirmed compromises. Rotate potentially exposed credentials and secrets, investigate managed hosts, and perform a full reinstallation where compromise is confirmed, as recommended by Vates.
🚩 Turla Deploys Cereal Malware to Steal Emails From Microsoft Exchange Servers
ESET Research identified a previously undocumented malware toolset called Cereal, attributed with high confidence to the Russia-aligned threat group Turla. The toolset was discovered in confirmed intrusions affecting government organizations in Kazakhstan and Romania. Designed for long-term cyberespionage, Cereal targets Microsoft Exchange servers using modular .NET components to execute commands, collect credentials, and intercept sensitive emails. In the Romanian intrusion, the malware was configured to collect messages involving NATO and European Union institutions.
Cereal uses a passive backdoor called CerealNeuron that receives encrypted commands through legitimate-looking Exchange web paths, eliminating the need for dedicated external command-and-control infrastructure. Other components exploit .NET execution mechanisms, DLL sideloading, and native image cache manipulation to execute malicious code within legitimate processes. Its CerealBox module injects into EdgeTransport.exe and intercepts selected email messages without registering a new Exchange transport agent. The activity represents confirmed exploitation of compromised Exchange environments, although the initial access method was not identified.
Impact: Successful deployment allows attackers to maintain covert access to Microsoft Exchange servers, collect sensitive communications, extract credentials, and perform internal reconnaissance. By intercepting messages within Exchange’s transport pipeline, Cereal can capture targeted emails while normal delivery continues, potentially exposing confidential government, diplomatic, and organizational information. Its use of legitimate Exchange processes and passive C2 communications may complicate detection through conventional network monitoring. Organizations operating compromised Exchange servers could face prolonged espionage activity without obvious service disruptions.
Recommendation:
-
Review Microsoft Exchange server activity for suspicious requests to /owa/sdds/, /AUTODISCOVER/PROXYSERVICE/, and /MICROSOFT-SERVER-ACTIVESYNC/INTEGRATED/API/, correlating them with unusual process or module activity.
-
Monitor Exchange transport processes for unexpected code injection or suspicious modules loaded into EdgeTransport.exe.
-
Investigate unauthorized DLL execution involving ncobjapi.dll or wbemcomn.dll within C:\Windows\System32\wbem\.
-
Inspect the .NET native image cache for unexpected assemblies or modified Exchange components, particularly files masquerading as Microsoft.Exchange.Search.Mdb.ni.dll.
-
Hunt for suspicious Exchange mailbox access, including unusual Exchange Web Services requests, targeted message collection, and encrypted email archives staged for exfiltration.
-
Review credential access and reconnaissance activity, particularly unexpected LSA Secrets extraction, Active Directory enumeration, and WMI queries originating from Exchange servers.
-
Apply ESET’s published indicators of compromise and investigate unusual .NET assembly execution or encrypted payload loading within legitimate Exchange and Windows processes.
🚩 CopperDragon-Linked Espionage Campaigns Target Global Telecom and Government Organizations
Check Point Research identified three cyberespionage activity clusters linked to CopperDragon, a suspected malware developer and supplier supporting China-nexus threat actors. The campaigns, tracked as SilentDelivery, OceanGate, and DarkWire, targeted telecommunications providers, government and military organizations, research institutions, and critical infrastructure across Latin America, Asia, and Europe. Researchers connected the operations through shared infrastructure characteristics and malware similarities within the cross-platform Sparrow framework.
The campaigns used different initial access techniques, including compromised internet-facing Linux servers and watering-hole attacks displaying fake Chrome certificate warnings to distribute malicious installers. Following compromise, attackers deployed backdoors including SquadC, SparrowDoor, SparrowShell, CopperDoor, and CopperDNS to maintain access, execute commands, harvest credentials, and move laterally. Researchers also observed trojanized SSH utilities, DLL sideloading, kernel rootkits, and DNS tunneling. These were confirmed intrusion campaigns, although CopperDragon’s role as a shared malware supplier remains an assessment rather than definitive attribution.
Impact: Successful compromise can provide attackers with persistent access to sensitive enterprise systems, enabling credential theft, surveillance, lateral movement, and data exfiltration. The campaigns demonstrate risks across both Windows and Linux environments, particularly where exposed infrastructure provides access to internal networks. Trojanized SSH components can capture administrative credentials, while kernel-level backdoors and encrypted communications may reduce detection visibility. Shared tooling across multiple threat actors also complicates attribution and incident scoping.
Recommendation:
-
Secure internet-facing infrastructure. Identify and remediate vulnerable Linux servers, restrict administrative access, and monitor for unauthorized SSH activity.
-
Monitor watering-hole activity. Investigate unexpected Chrome certificate warnings that instruct users to download installers, particularly files named CertFixer.msi.
-
Hunt for malicious persistence. Review Windows Registry Run keys for WindowsUpdateAssist, hidden administrator accounts such as admin$, and unauthorized Linux cron or systemd services.
-
Investigate credential theft. Monitor suspicious access to LSASS, unauthorized LSA security packages, and modifications to legitimate SSH or SSHD binaries.
-
Detect DLL sideloading and suspicious driver activity. Investigate unexpected winfsp.dll, libvlccore.dll, and ncpmif32.dll execution, alongside unauthorized WinDivert drivers or Linux kernel modules.
-
Review network communications. Hunt for unusual DNS MX queries, unauthorized SOCKS proxies, SSH tunnels, and connections to reported infrastructure, including amelicen[.]com, microsfot[.]vip, and windowsupdates[.]us.
-
Apply published indicators. Incorporate Check Point’s file hashes and network indicators into threat-hunting workflows, correlating matches with suspicious process execution and authentication activity.
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.




