Cisco Talos’ Vulnerability Discovery & Research team recently disclosed five vulnerabilities in Dell ControlVault 3 firmware and its associated Windows software, four vulnerabilities in Entr’ouvert Lasso, and one vulnerability in GL.iNet Slate AX.
For Snort coverage that can detect the exploitation of these vulnerabilities, download the latest rule sets fromSnort.org, and our latest Vulnerability Advisories are always posted onTalos Intelligence’s website.
Dell vulnerabilities
Discovered by Philippe Laulheret of Cisco Talos.
The Dell ControlVault is a hardware-based security solution designed for user authentication functions. Talos reported five vulnerabilities, as follows:
TALOS-2025-2173 (CVE-2025-31649) is a hard-coded password vulnerability. A specially crafted ControlVault API call can lead to an execution of privileged operation.
TALOS-2025-2174 (CVE-2025-31361) is a privilege escalation vulnerability. A specially crafted WinBioControlUnit API call can lead to privilege escalation.
TALOS-2025-2175 (CVE-2025-36460-CVE-2025-36463) covers multiple out-of-bounds read and write vulnerabilities. A specially crafted WinBioControlUnit API call can lead to memory corruption.
TALOS-2025-2188 (CVE-2025-32089) is a buffer overflow vulnerability. A specially crafted ControlVault API call can lead to an arbitrary code execution.
TALOS-2025-2189 (CVE-2025-36553) is a buffer overflow vulnerability. A specially crafted ControlVault API call can lead to memory corruption.
Entr’ouvert Lasso vulnerabilities
Discovered by Keane O’Kelley and another member of Cisco Advanced Security Initiative Group.
Lasso is a free (GNU General Public License) C library that defines processes for federated identities, single sign-on, and related protocols.
TALOS-2025-2193 (CVE-2025-47151) is a type confusion vulnerability, where a specially crafted SAML response can lead to an arbitrary code execution.
TALOS-2025-2194 (CVE-2025-46404),TALOS-2025-2195 (CVE-2025-46784), andTALOS-2025-2196 (CVE-2025-46705) are denial of service vulnerabilities. Specially crafted SAML responses can lead to a denial of service in all three cases.
GL.iNet Slate AX vulnerability
Discovered by Lilith >_> of Cisco Talos.
Slate AX (GL-AXT1800) is a Wi-Fi 6GB travel router. Cisco Talos discovered a firmware downgrade vulnerability,TALOS-2025-2230 (CVE-2025-44018), in the OTA Update functionality. A specially crafted .tar file can lead to a firmware downgrade. An attacker can perform a man-in-the-middle attack to trigger this vulnerability.
Welcome to this week’s edition of the Threat Source newsletter.
Back in April, I wrote about the risks of unintentionally leaking information while using search engines. Since then, I’ve been thinking: Life doesn’t just happen in front of a keyboard. There’s a social side, too (or so I’m told). With Thanksgiving around the corner, it seems the perfect time to flip the script and focus on a different but related concept: Care that you share.
For my non-American friends, who may be enjoying just another Thursday, stick with me. This season brings heightened risks everywhere. Many teams are running with skeleton crews, whether due to holiday mode (family, turkey, football, days off) or the year-end compliance push (hello, NIS2 and DORA). At the same time, on the other side of the fence, attackers ramp up their efforts; globally, Black Friday and similar events are peak periods for phishing campaigns, often targeting credentials with fake employee perk emails and other seasonal lures.
So, why emphasize “care that you share?”
Recently, I visited a university of applied sciences to give a guest lecture and learn more about the projects students are working on. It was a great experience, though preparing for an audience of students (not my usual crowd) was challenging. What do they already know? What topics interest them? Should I give them some history of STIX/TAXII? Geopolitical tensions? Honestly speaking, none of this was interesting to me when I was a student. I chose to start simple, discussing what threats and the DKIW pyramid were, and then focusing on CVE, CVSS, and KEV — one of my favorite topic clusters.
To my surprise, not only did the students engage and ask questions, but they also stuck around late on a Friday afternoon, diving into discussions about software supply chain risks and beyond. I don’t remember ever staying at university past 6:00 p.m. on a Friday as a student! A week later, when they presented their projects — many centered on authentication, TOTP, and SmartCards — I was genuinely impressed by their ideas and the real-world problems they were addressing.
“Care that you share” is a mindset that helps us appreciate the knowledge exchange that happens in person, too.
Whether sharing stories over dinner, IOCs over email, or ideas in a classroom, let’s all take a moment to consider not just what we share, but how and why we share it. I’ll admit, I sometimes hesitate to share certain stories myself, worried they might seem too obvious or uninteresting, or maybe even dumb. But more often than not, those moments of openness lead to the best conversations and new perspectives.
This rings especially true during busy or understaffed times, when teams are stretched thin. It’s tempting to keep things to ourselves to avoid “bothering” others. In reality, sharing a helpful tip, a concern, or just a quick update can make all the difference for colleagues who might be juggling extra responsibilities or missing context.
So this holiday season, care that you share. Thoughtful communication isn’t just about protecting information — it’s also about supporting each other, especially when resources are limited. You never know who might benefit from what you have to offer, yourself included.
The one big thing
Last week, Cisco Talos announced an initiative to retire outdated ClamAV signatures to reduce database sizes and improve efficiency by focusing on currently relevant threats. Starting Dec. 16, 2025, the “main.cvd” and “daily.cvd” databases will be cut roughly in half, offering smaller downloads and reduced resource usage. Retired signatures may be reintroduced if old threats reappear, and only supported ClamAV container images will remain available on Docker Hub to enhance security and management.
Why do I care?
Smaller signature databases mean faster updates, lower bandwidth and storage requirements, and improved performance, especially on resource-constrained systems. By focusing detection on active threats, ClamAV can more efficiently protect against current malware without being bogged down by obsolete signatures.
So now what?
We will continue to monitor the activity of retired signatures and will restore any that are needed to protect the community. Stay attentive and request the reinstatement of retired signatures if older threats reappear. In the meantime, we recommend that ClamAV container image users select a feature release tag rather than a specific minor release tag to stay up to date with security updates and bug fixes.
Top security headlines of the week
Second Sha1-Hulud wave affects 25,000+ repositories via npm preinstall credential theft The new supply chain campaign, dubbed Sha1-Hulud, has compromised hundreds of npm packages, uploaded to npm between November 21 and 23, 2025. The attack has impacted popular packages from Zapier, ENS Domains, PostHog, and Postman, among others. (The Hacker News)
FBI: Cybercriminals stole $262M by impersonating bank support teams Since January 2025, the FBI’s Internet Crime Complaint Center (IC3) has received over 5,100 complaints, with the attacks impacting individuals, as well as businesses and organizations across all industry sectors. (Bleeping Computer)
Everest ransomware claims breach at Spain’s national airline Iberia with 596 GB data theft The group states that the data covers millions of customers in multiple countries, and says it had long-term access with the ability to read and alter bookings. (HackRead)
CISA warns of active spyware campaigns hijacking high-value Signal and WhatsApp users CISA on Monday issued an alert warning of bad actors actively leveraging commercial spyware and remote access trojans (RATs) to target users of mobile messaging applications. (The Hacker News)
LINE messaging bugs open Asian users to cyber espionage Researchers discovered critical vulnerabilities that open the door to three main buckets of compromise: message replay attacks, plaintext and sticker leakage, and, most concerningly, impersonation attacks. (Dark Reading)
Can’t get enough Talos?
Talos Takes: When you’re told “no budget” From configuring what you already have, to open-source strategies, to the impact of cybersecurity layoffs, this episode is packed with practical guidance for securing your organization during an economic downturn.
Humans of Talos: On epic reads, lifelong learning, and empathy In this episode, Bill Largent shares what drew him to Talos, how his love of reading has shaped his cybersecurity ethos, and the key insights he shares for the next generation of cybersecurity professionals.
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-26 18:06:432025-11-26 18:06:43Care that you share
Stealers, loaders, and targeted campaigns dominated November’s activity. ANY.RUN analysts examined cases ranging from PNG-based in-memory loading used to deploy XWorm to JSGuLdr, a three-stage JavaScript-to-PowerShell loader pushing PhantomStealer.
Alongside these public cases, three Threat Intelligence Reports detailed new activity across Windows, Linux, and Android, including loader-enabled hijackers, Tor-based cryptotrojan communication, Linux ransomware in Go, MaaS stealers, and a WhatsApp-propagating campaign with geofencing controls.
Each case was analyzed inside ANY.RUN’s Interactive Sandbox, revealing execution flows, persistence mechanisms, and behavioral indicators that help teams tune detections and trace related activity.
Let’s break down how these attacks unfolded, where they hit, and what security teams can take away to strengthen their defenses before the next wave arrives.
1. XWorm: PNG Files Used as Containers for an In-Memory Loader
ANY.RUN analysts observed a new wave of XWorm infections in November, delivered through phishing pages and emails that distribute a JavaScript dropper named PurchaseOrder_25005092.js. While it appears benign at first glance, the script unpacks a full multi-stage chain designed to bypass quick checks, hide payloads inside PNG files, and execute a .NET assembly directly in memory.
How the attack begins
The campaign begins with a phishing lure (T1566.001) delivering a heavily obfuscated JavaScript installer (T1027). Once executed, the script checks whether the required components exist on the system and writes the missing files to C:UsersPUBLIC using Base64-encoded and AES-encrypted data (T1027.013). The staged components are later used during the PowerShell-driven decryption and in-memory execution stages.
The three staged files are:
Kile.cmd: A heavily obfuscated batch script filled with variable noise, percent-encoding, and fragmented Base64
Vile.png: Not an image but a Base64-encoded and AES-encrypted payload
Mands.png: Another encrypted data blob used during the second stage
Attackers deliberately use the “.png” extension (T1036.008) to make the files look harmless and evade quick manual reviews.
XWorm execution chain revealed with its 4 main steps
In-memory execution chain
After writing the staged components to C:UsersPUBLIC, the JavaScript dropper reconstructs readable commands from its fragments and launches a PowerShell payload (T1059). This PowerShell script operates as a two-stage AES-CBC loader.
Stage 1: Command runner
Reads C:UsersPUBLICMands.png as Base64 → AES-decrypt → yields Base64-encoded commands. Each command is decoded and executed via Invoke-Expression, enabling the script to run attacker-controlled instructions without a traditional executable.
Stage 2: In-memory assembly load
Reads C:UsersPUBLICVile.png as Base64 → AES-decrypt → raw bytes. Loader attempts to execute the resulting .NET assembly directly from memory (T1620).
This creates an in-memory loader that launches XWorm without dropping a traditional executable. A successful compromise enables credential theft, remote control, and lateral movement across corporate environments.
In November, ANY.RUN analysts identified JSGuLdr, a multi-stage loader that moves from JScript to PowerShell and ultimately deploys PhantomStealer. The chain relies on obfuscation, COM-based execution, cloud-hosted payloads, and in-memory loading, allowing the final payload to run with limited on-disk exposure.
JSGuLdr execution chain with the final delivery of PhantomStealer
Stage 1: JScript Execution and COM-Based PowerShell Launch
The first stage is an obfuscated JScript file signed with a fake Authenticode certificate to appear trustworthy (T1027, T1553.006). It generates an encrypted PowerShell string and writes it to %APPDATA%Registreri62, forming the second-stage component.
Execution then shifts to Shell.Application and Explorer COM interaction, which launches powershell.exe under explorer.exe, masking the activity as normal user behavior (T1559.001, T1218).
Stage 2: PowerShell Loader, Cloud Retrieval, and In-Memory Execution
The PowerShell code decodes the contents of Registreri62, reconstructs hidden commands, and downloads an encrypted payload from Google Drive using a WebClient request (T1105). This payload is stored as %APPDATA%Autorise131.Tel, used as the on-disk container for the next stage (T1074.001).
Stage 3: In-Memory Loading and PhantomStealer Injection
PowerShell decrypts Autorise131.Tel, extracts raw bytes, and loads the resulting .NET assembly directly in memory (T1620). The final payload, PhantomStealer, is then injected into msiexec.exe, allowing it to run under a trusted Windows process and steal data without creating a conventional executable on disk (T1055, T1218.007).
ANY.RUN sandbox reveals full execution chain of JSGuLdr
Track similar activity with TI Lookup
Use the following TI Lookup query to identify related JSGuLdr activity, pivot from shared IOCs, and uncover additional loader variants across recent submissions.
This Threat Brief provides a focused breakdown of three active threats, including how each sample behaves in the sandbox, its persistence and execution patterns, and the key detection points analysts can rely on. The report includes details about process activity, file system changes, network behavior, and extracted indicators, along with TI Lookup queries tailored to each malware family; PDFChampions’ mutex-based signature, Efimer’s Tor-based curl command, and BTMOB’s Android configuration file.
TI report revealing PDFChampions, Efimer, and BTMOB
PDFChampions (Windows)
A browser hijacker distributed via malvertising that also acts as a loader. It changes the default search engine, terminates competing browsers, and can download and run additional payloads directly in memory.
Detection note: identify activity via the mutex “Champion.”
A cryptocurrency-focused trojan spread through phishing and compromised WordPress sites. It steals wallets and credentials and uses curl.exe to reach a Tor-hidden C2 endpoint (.onion/route.php). Detection note: monitor curl connections to .onion/route.php. TI Lookup:commandLine:”curl.exe*.onion/route.php”
BTMOB RAT (Android)
An Android RAT sold as MaaS. It abuses Accessibility Services for full device control, records screen and audio, and targets financial apps. Distributed through phishing APKs.
Detection note: presence of BTConfig.xml in the app’s shared preferences.
This month’s Threat Brief examines three threats in detail, with execution-flow screenshots, detection indicators, persistence artifacts, and public-sample telemetry. The report also provides ready-to-use TI Lookup queries and IOCs so teams can expand visibility and identify similar cases in their environments.
TI report revealing Monkey, Phoenix, and NonEuclid
Monkey (Linux)
Monkey is a Go-based x64 ELF ransomware that disables security controls, establishes persistence through cron, rc.local, and systemd, collects system information, and encrypts files with a .monkeyRansomware extension. It also drops a ransom note and changes the system wallpaper.
Detection note: creation of /etc/systemd/system/monkey.service.
Phoenix is a Windows backdoor delivered as a second-stage payload in targeted email campaigns. It creates a mutex, copies itself for persistence, gathers system information, and communicates with its C2 via WinHTTP. The malware also uses process injection during execution.
Detection note: dropped binary sysProcUpdate.exe used for injection.
NonEuclid is a C# RAT with persistence, AMSI and Defender bypass, anti-VM checks, UAC bypass, and optional AES-based file encryption using the .NonEuclid extension. Sold as a crimeware kit, it combines remote control features with ransomware capabilities and uses obfuscated strings and NTSTATUS codes that can be detected via a dedicated YARA rule. Detection note: YARA detection based on obfuscated Unicode strings and NTSTATUS markers.
Threat Intelligence Report 3: Valkyrie, Sfuzuan, and Sorvepotel
This Threat Brief examines three Windows-based threats with different infection vectors and persistence patterns. The report includes sandbox screenshots, process activity, on-disk artifacts, and TI Lookup queries for tracking related behavior across public submissions.
TI report revealing Valkyrie, Sfuzuan, and Sorvepotel
Valkyrie (Windows)
Valkyrie is a credential-stealing MaaS platform linked to Prysmax. It collects browser and system data, stores temporary output in Valkyrie.zip under the Temp directory, and exfiltrates the archive to a remote C2. Detection is possible through the Temp-path signature or a dedicated YARA rule included in the report.
Sfuzuan is a backdoor distributed through multiple, unrelated sources. It bypasses system protections to gain access, gathers system and location details, and connects to a set of rotating command-and-control domains. The malware drops a distinctive TXT file that serves as a reliable detection point.
Sorvepotel is a self-propagating campaign spread through WhatsApp messages containing malicious ZIP archives. After launch, it uses PowerShell and VBS scripts for execution and persistence, creates scheduled tasks, and automatically sends the same archive to all WhatsApp Web contacts. The campaign targets Portugal and Brazil using geofencing based on IP and system language.
Empower Your SOC with Real-Time Behavioral Insights
Multi-stage loaders, encrypted payload containers, and region-aware campaigns are getting harder to catch with static filtering alone. While these threats unfold across PowerShell chains, COM-triggered executions, Linux services, or Android components, attackers move quickly, and manual triage can’t keep up. ANY.RUNgives SOC teams the behavioral visibility they need to respond at the speed of modern attacks.
Here’s how teams stay ahead:
Surface hidden execution paths immediately: Detonate loaders, encrypted payloads, and cloud-hosted components inside a live VM and watch each stage, JavaScript, PowerShell, .NET, Linux services, or APK behavior, as it unfolds.
Shorten investigation time: Automated unpacking, network tracing, and live indicators turn multi-stage chains into readable timelines, reducing time spent reversing obfuscated scripts or in-memory loaders.
Catch stealthy techniques earlier: From fileless PowerShell commands to COM-based execution and WhatsApp-triggered propagation, behavioral cues expose activity that traditional tools overlook.
Strengthen detections with instant enrichment: Use Threat Intelligence Lookup to pivot from a single IOC, file path, mutex, command line, or domain, to related submissions and shared TTPs across hundreds of cases.
Feed continuous intelligence into your stack: Integrate Threat Intelligence Feeds with your SIEM, SOAR, or XDR to keep detections updated as new loader variants, stealer kits, and region-specific campaigns emerge.
For SOC teams, MSSPs, and threat researchers, ANY.RUN provides the depth and real-time visibility needed to investigate faster, validate threats quickly, and turn emerging behaviors into reliable detection logic.
ANY.RUN supports more than 15,000 organizations worldwide across finance, healthcare, telecom, retail, and technology, helping security teams investigate threats with clarity and confidence.
Built for speed and deep visibility, the solution combines interactive malware analysis with live threat intelligence, allowing SOC analysts to observe real execution behavior, extract indicators, and understand attacker techniques in seconds.
By integrating ANY.RUN’s Threat Intelligence suite into existing security workflows, teams can accelerate investigations, reduce uncertainty during incidents, and strengthen resilience against fast-evolving malware families and multi-stage attack chains.
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-26 10:06:402025-11-26 10:06:40Major Cyber Attacks in November 2025: XWorm, JSGuLdr Loader, Phoenix Backdoor, Mobile Threats, and More
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-26 06:06:392025-11-26 06:06:39Influencers in the crosshairs: How cybercriminals are targeting content creators
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-25 13:06:392025-11-25 13:06:39MDR is the answer – now, what’s the question?
Alert overload is one of the hardest ongoing challenges for a Tier 1 SOC analyst. Every day brings hundreds, sometimes thousands of alerts waiting to be triaged, categorized, and escalated. Many of them are false positives, duplicates, or low-value notifications that muddy the signal.
When the queue never stops growing, even experienced analysts start losing clarity, missing patterns, and risking oversight of critical threats.
Beyond Burnout: How Alert Fatigue Destroys Careers
Alert overload isn’t just unproductive — it’s toxic. Constant false positives create chronic stress, anxiety, and decision fatigue. Analysts doubt themselves, experience imposter syndrome, and burn out fast. Many leave the industry within years, citing mental health tolls like sleep loss and eroded confidence from missing “the big one” amid the chaos.
Tier 1 analysts who triage efficiently using context gain sharp investigation skills, earn trust for escalations, and accelerate to Tier 2/3 roles. They avoid burnout, stay passionate about cybersecurity, and position themselves as indispensable experts in a high-demand field. Solutions like ANY.RUN’s Threat Intelligence Lookup can provide a master key not only to an analyst’s career, but to the next level of SOC efficiency.
Cutting Through the Chaos: How Threat Intelligence Keeps Analysts Effective
Alert overload at Tier 1 creates bottlenecks: unnecessary escalations flood senior analysts, response times balloon, and real breaches slip through. This drains budgets on prolonged incidents, erodes team morale, and weakens organizational defenses, turning a proactive SOC into a reactive firefighting unit.
Threat intelligence gives analysts the missing piece they often need during triage: context. Instead of manually searching for data across multiple sources, TI instantly tells you what the alert is truly about.
Was this domain seen in phishing attacks? Is this hash connected to a malware family? Is the mutex associated with known malicious samples?
With enriched data, Tier 1 analysts spend less time guessing and more time making confident decisions. Context transforms alerts from ambiguous into actionable and significantly reduces both cognitive load and triage time.
The key is having threat intelligence that’s immediately accessible during your investigation workflow, comprehensive enough to cover the indicators you encounter, and current enough to reflect the latest threat landscape. When used effectively, threat intelligence doesn’t just help you process alerts faster. It improves your accuracy, reduces the anxiety of uncertainty, and helps you develop the threat intuition that distinguishes experienced analysts.
Context on Demand: Understand an Alert Fast
ANY.RUN’s Threat Intelligence Lookup provides immediate, precise context from one of the largest ecosystems of analyst-generated data worldwide. It connects information from 15,000+ SOCs and security teams and presents it in a clean, friendly format.
Search IOC, find context, verdicts, and malware samples
Stop guessing. Get instant context on any IOC in 3 seconds.
Try TI Lookup in your SOC workflows.
Instead of digging through scattered reports, teams get immediate answers: malware classification, sample behavior, network connections, relationships, and IOCs — all based on real sandbox runs.
This dramatically shortens triage time and reduces the chance of overlooking critical details hidden inside the noise.
Real-World Wins: See TI Lookup in Action
From Vague Domain to Clear Verdict
An alert flags a weird domain in network traffic. Paste it into ANY.RUN TI Lookup: instantly reveal if it’s a known C2 server, tied to ransomware like LockBit, with resolved IPs, associated hashes, and full attack chains from recent sandbox runs. Result? Confident closure or escalation, saving hours and stopping lateral movement cold.
Check domain, reveal malware family and campaigns in progress
How To Make a Hash Talk
EDR alerts on a dropped executable hash. Query TI Lookup: uncover the exact malware family (e.g., RedLine stealer), prevalence stats, extraction TTPs, and behavioral details from detonations. Benefit: Precise containment (block similar hashes), updated detections, and proof for stakeholders: no deep dives needed.
A process creates an odd mutex (mutual exclusion object). Search it in TI Lookup’s synchronizations tab: link it to families like DCRat or AsyncRAT, view creating processes, and jump to sandbox sessions showing persistence tactics. Outcome: Rapid hunting across endpoints, stronger YARA rules, and blocking reinfection before damage spreads. syncObjectName:”*sm0:4360:304:wilstaging_02″
Mutex lookup results: links to malware families and samples
Stop Surviving Alerts. Start Dominating Them
Alert overload is not an inevitable curse of SOC work, it’s a solvable problem that demands both systemic improvements and individual strategy.
The difference between analysts who burn out and those who thrive often comes down to their ability to extract context quickly, make confident decisions, and focus their limited time on high-value investigations. Threat intelligence platforms like ANY.RUN’s Threat Intelligence Lookup are not magic solutions that eliminate alerts, but they are force multipliers that transform your effectiveness by providing the context that turns ambiguous indicators into clear decisions.
Cut through alert noise with one lookup.
Enrich IOCs instantly and triage faster.
By integrating threat intelligence into your daily workflow, you reduce investigation times from minutes to seconds, improve accuracy by relying on aggregated community knowledge, and build the pattern recognition skills that define senior analysts. The critical incidents hiding in your alert queue will only become visible when you clear away the noise efficiently enough to spot them.
Take control of your alerts before they control you, leverage the intelligence resources available to you, and remember that becoming a great analyst isn’t about handling every alert. It’s about handling the right alerts in the right way.
FAQ
1. Why is alert overload especially dangerous for Tier 1 analysts?
Tier 1 analysts are the first responders to every alert. High volume, repetitive tasks, and time pressure make it easy to overlook critical incidents and lead to burnout, stress, and reduced accuracy.
2. How does alert overload impact the quality of SOC operations?
Overwhelmed analysts escalate incorrectly, miss key signals, and slow down triage. This cascades across the SOC, delaying incident response and weakening the organization’s security posture.
3. What role does threat intelligence play in reducing alert overload?
Threat intelligence adds immediate context to alerts, helping analysts understand whether an IOC is benign or malicious without manual research. This shortens triage time and reduces cognitive load.
4. What makes ANY.RUN’s TI Lookup useful for Tier 1 analysts?
TI Lookup provides fast, behavior-based context from millions of real sandbox runs. Analysts can check domains, hashes, IPs, and mutexes in seconds and see relationships, malware families, and activity patterns.
5. Can TI Lookup help analysts avoid unnecessary escalations?
Yes. By revealing whether an indicator is tied to known malware, seen in threats before, or associated with clean activity, TI Lookup allows analysts to make confident classification decisions.
6. What types of indicators can TI Lookup enrich?
TI Lookup supports enrichment for domains, URLs, IP addresses, file hashes, mutexes, and many other IOCs, each supplemented by sandbox-based behavioral insights and real analyst data.
7. How does TI Lookup help prevent career burnout for analysts?
By reducing guesswork and manual searching, TI Lookup lowers stress, improves accuracy, and helps analysts manage workloads more sustainably — supporting long-term career growth instead of fatigue-driven turnover.
About ANY.RUN
ANY.RUN is a leading provider of interactive malware analysis and threat intelligence solutions. Today, 15,000+ organizations worldwide use ANY.RUN to speed up investigations, strengthen detection pipelines, and give their teams a clearer view of what’s really happening on their endpoints.
SOC teams using ANY.RUN report measurable improvements, including:
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-25 11:07:082025-11-25 11:07:08How to See Critical Incidents in Alert Overload: A Guide for SOCs and MSSPs
We recently detected a new malicious campaign that employs a rather intriguing approach. The actor creates their own signed builds of a legitimate remote access tool. To distribute them, they use an AI-powered service to mass-generate malicious web pages that convincingly masquerade as the official sites of various applications.
Read on to find out how this attack works, why it’s particularly dangerous for users, and how to protect yourself.
How the attack works
It appears that the malicious actor is utilizing several launchpad options for their attacks. First, they are clearly banking on a significant number of users landing on their fake pages through simple Google searches. This is because the fake sites most often have addresses that match — or are very close to — what users are searching for.
Looking through Google search results, you can sometimes catch a bunch of Pokémon fake sites masquerading as legitimate ones. In this case, we’re looking at Polymarket clones.
Second, they employ malicious email campaigns as an alternative. In this scenario, the attack kicks off with the user getting an email that contains a link to a fake website. The content might look something like this:
Dear $DOP holders,
The migration window from DOP-v1 to DOP-v2 has officially closed, with over 8B+ tokens successfully migrated.
We're excited to announce that the DOP-v2 Claim Portal is now OPEN!
All $DOP holders can now visit the portal to securely claim their tokens and step into the next phase of the ecosystem.
Claim Your DOP-v2 Tokens Now https://migrate-dop[dot]org/
Welcome to DOP-v2 — a stronger, smarter, and more rewarding chapter begins today.
Thank you for being part of this journey.
The DOP Team
Some of the malicious pages we discovered in this campaign masquerade as the websites of antivirus or password management applications. Their content is clearly designed to scare the user with fake warnings about some kind of security issue.
A fake Avira website warns of a vulnerability and offers to download an “update”
So, the attackers are also leveraging a well-known tactic known as scareware: foisting an unsafe application on users under the guise of protection against an imaginary threat.
A fake Dashlane page warns of a “high-severity encryption-metadata exposure affecting cloud relay synchronization”, whatever that’s supposed to mean. And of course, you can’t fix it unless you download something
Fake websites built with Lovable
Despite differences in content, the fake websites involved in this malicious campaign share several common features. For starters, their addresses are most often constructed according to the formula: {popular app name} + desktop.com — a URL that closely matches an obviously common search query.
Besides, the fake pages themselves look quite professional. Interestingly, the appearance of the fake sites doesn’t exactly replicate the design of the originals — these are not direct clones. Rather, they are very convincing variations on a theme. As an example, we can look at some fake versions of the Lace crypto wallet page. One of them looks like this:
The first variant of the fake Lace website
And the other looks like this:
The second variant of the fake Lace website
The original Lace website looks a lot like these fakes, but it still differs from them in many obvious ways:
The real Lace website is simultaneously similar and dissimilar to the fake versions. Source
It turns out the attackers have weaponized an AI-powered web builder to create fake pages. Because the attackers cut corners and inadvertently left a few tell-tale artifacts, we managed to identify the exact service they are leveraging: Lovable.
Using an AI tool allowed them to significantly reduce the time required to create a fake, thereby churning out forgeries on an industrial scale.
Syncro remote administration tool
Another common feature of the fake sites involved in this campaign is that they all distribute the exact same payload. The malicious actor neither created their own Trojan nor bought one off the black market. Instead, they are using their own build of a perfectly legitimate remote access tool, Syncro.
The original app facilitates centralized monitoring and remote access for corporate IT support teams and managed service providers (MSPs). Syncro services are relatively inexpensive, starting at $129 per month with an unlimited number of managed devices.
Fake Yoroi crypto wallet site
At the same time, the tool possesses serious capabilities: in addition to screen sharing, the service also provides remote command execution, file transfer, log analysis, registry editing, and other background actions. However, Syncro’s main appeal is a simplified installation and connection process. The user — or, in this case, the victim — only has to download and run the installation file.
From that point, the installation runs completely in the background, secretly loading a malicious Syncro build onto the computer. Because this build has the attacker’s CUSTOMER_ID hardcoded, they instantly gain full control over the victim’s machine.
The Syncro installer window flashes on the screen for mere seconds, and only a keen-eyed user might notice that the wrong software is being set up.
Once Syncro is installed on the victim’s device, the attackers gain full access and can use it to achieve their objectives. Given the context, these appear to be stealing crypto wallet keys from victims and siphoning off funds into the attackers’ own accounts.
Another fake site, now for the Liqwid DeFi protocol. Although Liqwid offers only a web application, the fake site allows users to download versions for Windows, macOS, and even Linux
How to protect yourself against these attacks
This malicious campaign poses a heightened threat to users for two main reasons. First, the fake sites crafted with the AI service look quite professional, and their URLs aren’t overly suspicious. Of course, both the design of the fake pages and the domains used differ noticeably from the real ones, but this only becomes apparent in direct comparison. At a glance, however, it’s easy to mistake the fake for the original.
Second, the attackers are using a legitimate remote access tool to infect users. This means that detecting the infection can be difficult.
Our security solution has a special verdict, Not-a-virus for cases like this. This verdict is assigned, among other things, when various remote access tools — including the legitimate Syncro — are detected on the device. As for Syncro builds used for malicious purposes, our security solution detects them as HEUR:Backdoor.OLE2.RA-Based.gen.
It’s important to remember that an antivirus won’t block all legitimate remote administration tools by default to avoid interfering with intentional usage. Therefore, we recommend that you pay close attention to notifications from your security solution. If you see a warning that Not-a-virus software has been detected on your device, take it seriously and, at the very least, check which application triggered it.
If you have Kaspersky Premium installed, use the Remote Access Detection feature — and, if necessary, the app removal option — that come with your premium subscription. This feature detects around 30 of the most popular legitimate remote access applications, and if you know you didn’t install them yourself, that is cause for concern.
Further recommendations:
Don’t download applications from dubious sources, especially on devices with financial or crypto apps installed.
Always double-check the addresses of the pages you’re visiting before performing any potentially dangerous actions like downloading an app or entering personal data.
Pay close attention to warnings from the antivirus and anti-phishing defenses built into our security solutions.
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-21 17:06:552025-11-21 17:06:55Syncro + Lovable: RAT delivery via AI-generated websites | Kaspersky official blog
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-21 03:06:382025-11-21 03:06:38The OSINT playbook: Find your weak spots before attackers do
Welcome to this week’s edition of the Threat Source newsletter.
This week, we explore how advances in agentic AI are rapidly transforming the cyber crime business.
Agentic AI programming gives AI agents autonomy, allowing them to interact with external systems to collect information, make decisions with the help of a generative AI system, and then effect changes in the external environment. The activity takes place through various APIs according to the instructions provided to the agent and in the context of a defined workflow.
The advantage for human operators is that these systems can efficiently execute routine activities that would otherwise require accessing multiple systems. Essentially, the AI agent acts as a trusted assistant who is able to get on with things with minimal supervision while the human operator can focus on other things.
As this approach brings advantages to the legitimate economy, so it brings similar efficiencies to the cyber crime economy. More recently, the publication of the discovery of the first AI-orchestrated cyber campaign should give us pause. It signals a new era for cybersecurity teams.
We’re entering a time when we can expect to see much experimentation and innovation with AI in both the legitimate and cyber crime economies. AI can act as a force enabler, making tasks easier and faster to perform. Similarly, AI can lower barriers to entry, allowing lower skilled actors to perform tasks that they lack the skills to perform. While AI does not bring new capabilities, it can make existing capabilities easier to execute. However, AI systems still require skillful instruction and supervision.
AI is not infallible, it gets things wrong, and it is prone to inventing nonsense. When it does go off the rails, a human needs to step in and resolve the situation. This is not necessarily easy to do and may prove tricky for low-skilled threat actors.
Don’t be discouraged: We can also leverage these developments to our advantage. Defensive teams can write their own agentic systems to find and fix weaknesses in their own systems before malicious actors identify them. We can deploy honeypot systems designed to be found by malicious AI systems, engage with them and tie up their resources.
The threat landscape has never been static. While AI does make some tasks more accessible to threat actors, it is a double-edged sword and also brings opportunities to defenders.
The one big thing
Cisco Talos has introduced new features for Snort3 users within Cisco Secure Firewall. A new “Severity” rule group allows you to organize detection rules by CVSS-based vulnerability severity (low, medium, high, critical). This allows teams to better prioritize and manage rules according to risk and urgency. You can also select rules based on vulnerability age (e.g., last 2, 5, or 10 years).
Why do I care?
This update allows you greater flexibility and control. It makes it simpler to maintain consistent, targeted detection coverage, whether you’re running large, distributed networks or smaller environments with tailored security priorities.
So now what?
Review your current Snort3 rule configurations in Cisco Secure Firewall and consider adopting the new Severity and time-based grouping features. By tailoring rule sets to your organization’s specific risk tolerance and patching cycles, you can optimize detection coverage, streamline management, and better protect your environments.
Top security headlines of the week
Criticalrailwaybrakingsystemsopen totampering Researchers have figured out how to spoof the signals that tell train conductors to brake, opening the door to any number of dangerous attack scenarios. (Dark Reading)
EchoGramflaw bypasses guardrails in major LLMs A flaw discovered in early 2025 and dubbed EchoGram allows simple, specially chosen words or code sequences to completely trick the automated defences, or guardrails, meant to keep the AI safe. (HackRead)
Over 67,000 fakenpmpackages flood registry in worm-like spam attack The worm-life propagation mechanism and the use of a distinctive naming scheme that relies on Indonesian names and food terms for the newly created packages have lent it the moniker IndonesianFoods Worm. The bogus packages masquerade as Next.js projects. (The Hacker News)
Cornerstone Staffing ransomware attack leaks 120,000 resumes, claimsQilingang The notorious Qilin gang posted the industry-leading recruitment agency on its dark leak blog last Thursday. The group claims to have exfiltrated 300GB of sensitive information from Cornerstone. (Cybernews)
Surveillance tech providerProteiwas hacked, its data stolen, and its website defaced It’s not clear exactly when or how Protei was hacked, but a copy of the company’s website saved on the Internet Archive’s Wayback Machine shows it was defaced on November 8 and restored soon after. (TechCrunch)
Can’t get enough Talos?
The TTP: How Talos built an AI model into one of the internet’s most abused layers Hazel talks with Talos researcher David Rodriguez about how adversaries use DNS tunneling to sneak data out of networks, why it’s so difficult to spot in real time, and how Talos built an AI model to detect it without breaking anything important (like the internet).
Humans of Talos: On epic reads, lifelong learning, and empathy In this episode, Bill Largent shares what drew him to Talos, how his love of reading has shaped his cybersecurity ethos, and the key insights he shares for the next generation of cybersecurity professionals.
Unleashing the Kraken ransomware group In August 2025, Cisco Talos observed big-game hunting and double extortion attacks carried out by Kraken, a Russian-speaking group that has emerged from the remnants of the HelloKitty ransomware cartel.
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-20 20:06:502025-11-20 20:06:50It’s not personal, it’s just business
In many SOCs, phishing analysis still follows the same old pattern: manually pull apart URLs, inspect attachments by hand, take screenshots, collect indicators one by one… and hope nothing slips through in the process. It’s careful work, but slow.
Every step analysts normally handle themselves is condensed into a few seconds of automated detonation, real-time behavior tracking, and instant IOC extraction. That’s how a 15-minute job becomes a 60-second answer.
How Phishing Analysis Really Works: With vs. Without a Sandbox
Once the email is flagged as suspicious, analysts usually move through a predictable checklist: review the link or attachment, open it inside a safe environment, observe what happens, and extract indicators manually. Each phase takes time, and even small tasks, decoding a URL, grabbing a screenshot, checking a redirect; slow the investigation down.
When the same message is detonated inside ANY.RUN sandbox, the whole chain is captured automatically. The VM loads the content, follows redirects in real time, records every network request, and pulls out indicators as soon as the activity appears. Instead of digging piece by piece, analysts simply watch the behavior unfold and confirm the verdict.
A good example of this speed is a recent phishing case where attackers used Figma pages to kick off a credential-harvesting chain. Inside the sandbox, the entire Figma → Microsoft microdomain → Azure Blob Storage flow becomes visible in under a minute.
Without a sandbox: Analysts usually begin by checking links manually, opening attachments in a VM environment, or trying to reproduce the user’s click path. Even simple emails take time to decode and verify, often adding up to 5–10 minutes before any real behavior is observed.
With a sandbox: Upload the email or attachment, and the sandbox detonates it instantly inside a controlled VM. Initial behavior, connections, redirects, script execution, appears in 20–40 seconds, giving analysts a fast idea of whether the file is benign or dangerous.
2. Behavior Observation
Without a sandbox: Once the link or attachment is opened in a controlled VM, analysts have to follow the behavior manually; redirects, process launches, hidden scripts, background network calls. None of it is being tracked in a custom VM deployed locally by default.
The workflow is slow because everything happens in small pieces that need to be captured one by one. Depending on the complexity of the email, this phase can take anywhere from several minutes to well over ten, especially if the chain includes multiple hops or short-lived activity.
With a sandbox:
ANY.RUN’s process tree with a clear hierarchy showing every spawned process and its relationships
The moment the detonation starts, the sandbox records each action as it happens. Processes, redirects, and network requests appear live in the interface, so analysts see the full flow without chasing events across different tools. In most cases, the main behavior is already visible within 20–40 seconds, including activity that would be easy to miss during observation in a custom VM.
3. IOC Extraction
Without a sandbox: Collecting indicators is usually one of the most time-consuming parts of phishing analysis. Analysts have to pull out every domain, IP address, hash, and dropped file path manually, sometimes by repeating the execution to catch fast or hidden activity. Cross-checking each indicator across logs, browsers, and tools can stretch this phase to 5–10 minutes or more, especially when the redirect chain is long.
With a sandbox:
All IOCs extracted in one place for fast, focused analysis inside ANY.RUN
Indicators appear as soon as the activity occurs. Domains, IPs, file hashes, registry changes, and dropped objects are captured automatically and displayed in a single view. Instead of hunting for details, analysts simply review the list. This typically takes 10–20 seconds, even when multiple indicators are created during detonation.
4. Threat Matching
Without a sandbox: After gathering indicators, analysts typically check each domain, IP, and file hash in external reputation portals or TI sources. Moving between tools and validating each indicator one by one often adds 5–10 minutes, especially when the phishing chain produces several IOCs.
With a sandbox: Reputation details appear automatically as soon as indicators show up. The ANY.RUN sandbox displays the name of the threat, whether it is a malware family, a phishing kit, or even an APT. The threat coverage is continuously updated by ANY.RUN’s in-house team of threat hunters, researchers, and analysts.
Relevant clickable labels and Trends Tracker for deeper analysis of the threat
Suspicious findings are also labeled with clickable threat names, allowing analysts to jump directly to related public submissions for deeper comparison. Besides, a link to the Malware Trends Tracker provides broader context, showing how the threat behaves across other samples.
What normally requires several manual lookups takes 10–20 seconds, because the essential context is already available in the interface.
5. Incident Documentation
Without a sandbox: Documenting findings is one of the most tedious parts of phishing analysis. Analysts need to capture screenshots, save URLs, gather indicators, describe behavior, and assemble everything into a ticket or report by hand. Even when the case is simple, this often requires 5–10 minutes, and much longer when multiple steps or redirects are involved.
With a sandbox: A complete report is generated automatically as the detonation runs. Screenshots, network activity, redirects, process events, indicators, and threat labels are all captured and stored in a structured format.
Auot-generated report with gathered IOCs, TTPs, behavior details, screenshots, and more
Analysts can export the report instantly or link directly to it, so the case can move forward without manual writing or screenshot collection. This entire phase usually takes 10–20 seconds, since the documentation is created for you.
The Time Difference: 15 Minutes vs. 60 Seconds
When you put each step side by side, the gap becomes obvious. Manual phishing analysis breaks the workflow into several slow checks, while an interactive sandbox condenses everything into one fast detonation.
Step
Without a Sandbox
With a Sandbox
URL / Attachment Analysis
5–10 minutes
20–40 seconds
Behavior Observation
10–15 minutes
20–40 seconds
IOC Extraction
5–10 minutes
10–20 seconds
Threat Matching
5–10 minutes
10–20 seconds
Incident Documentation
5–10 minutes
10–20 seconds
Total Time
~15 minutes
~60 seconds
What’s usually a long, repetitive workflow turns into a one-minute verdict. When a phishing wave hits and dozens of suspicious emails land in the queue, those saved minutes quickly add up, often freeing hours across a single shift.
Why This Speed Counts: The Business Impact Behind the Numbers
Cutting phishing analysis from 15 minutes to 60 seconds drives measurable improvements across the entire SOC.
90% of malicious activity is exposed within the first 60 seconds of detonation → analysts see the real behavior before the attacker has time to hide it
94% of users report faster triage → fewer tasks stuck in the queue, fewer delays during active phishing waves
SOCs that adopt interactive sandboxing see up to a 3× boost in investigation throughput → more cases closed per shift, less pile-up when suspicious emails spike
False-positive noise drops significantly → threat analysts spend more time on real signals and less on dead ends
Teams report up to a 58% increase in threats identified overall, including attacks that bypass other controls → behavioral visibility picks up what static checks miss
This combination, fast verdicts, clear behavior visibility, and automated context, transforms phishing analysis from a slow manual chore into a fast, reliable, repeatable process.
Want to see how your SOC can speed up phishing investigations?
Discover how interactive analysis cuts investigation time and exposes phishing behavior in under a minute.
ANY.RUN helps security teams investigate threats faster and with far greater clarity. The Interactive Sandbox reveals full attack behavior in real time, from process execution and redirects to network activity and dropped files, giving analysts the visibility they need to make confident, evidence-based decisions.
Cloud-based and ready to use, ANY.RUN supports Windows, Linux, and Android environments, making it easy to analyze phishing emails, URLs, and malware without managing complex infrastructure.
Its Threat Intelligence Lookup and continuously updated TI Feeds provide automation-ready indicators that strengthen detection, enrichment, response, and reporting across security operations.
Together, these capabilities give analysts a fast, transparent, and reliable way to understand modern attacks and improve overall SOC performance.
https://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.png00adminhttps://www.backbox.org/wp-content/uploads/2018/09/website_backbox_text_black.pngadmin2025-11-20 10:06:432025-11-20 10:06:43Detected in 60 Seconds: How to Identify Phishing with a Malware Sandbox