Search/trendmicro
Vendor

trendmicro

Known CVEs
0
Highest CVSS
In KEV
0
Vendor
officescan cloud
Connections
118 relationships
Gaming the system: how a Chinese-speaking actor turned Brazilian government sites into an SEO weapon
Research by: Amit Yardeni Key Points A Chinese-speaking actor is now targeting Brazil.  Check Point Research has uncovered a sustained campaign against Brazilian organizations, primarily government and educational institutions since mid-2025. We dubbed this group Gambling Goblin: a Chinese-speaking cybercrime cluster connected to a previously documented group, Earth Berberoka, that targeted gambling sites across Asia. It marks a shift from Brazil’s usual home-grown banking-trojan threats to a foreign operator moving in Compromised web servers turned into stealthy proxies.  The attackers compile and install malicious Apache modules on victim servers that silently reverse-proxy visitors to attacker-controlled phishing pages, while the traffic still appears to originate from the legitimate domain, with the site’s own security headers stripped so injected content runs freely. Large-scale SEO manipulation.  The phishing pages pose as trusted app stores such as Google Play, Microsoft Store, and Amazon. Behind that facade, they push online gambling and sports betting, and they chain together compromised high-reputation domains, many of them Brazilian government sites, to inflate search rankings and hijack traffic at scale. A broad, heavily obfuscated Linux toolkit.  Once inside a host, the group deploys custom tools – downloader ( DownPro ), multiple backdoors including the modular  AlphaAgent  and the  oRAT  RAT, a 3snake-based credential stealer, an SSH brute-forcer, and a plugin-driven reconnaissance agent. Most of them are wrapped in packing and virtualization layers to slow analysis and evade detection. The operation reaches well beyond Brazil.  We identified parallel phishing networks localized in Vietnamese, Spanish, and English, alongside infrastructure that generates fresh domains daily – evidence the model is built to scale and be exported to new regions. One step from direct malware delivery.  Because the pages already mimic app-download destinations, the same infrastructure sits a single configuration change away from pushing malware straight to victims, a latent escalation risk beyond the current search-fraud scheme. Introduction Since mid-2025, Check Point Research has tracked a sustained campaign against Brazilian organizations. The tradecraft points to a Chinese-speaking cybercrime group connected to Earth Berberoka, an actor first  documented  targeting gambling sites across Asia. Once inside a victim, the group deploys a broad Linux toolkit: a custom downloader, several backdoors, and familiar offensive utilities. Most of it arrives heavily obfuscated – wrapped in layered virtualization and packing to slow analysis and evade detection. The purpose becomes clear at the network layer. The attackers install custom Apache modules that quietly proxy visitors to a sprawling set of phishing pages. Many of those pages sit on Brazilian government domains that appear to have been compromised and repurposed without their owners’ knowledge. The reach extends beyond Brazil. We uncovered a second phishing network run by the same actor; this one is built for Vietnamese victims. The likely goal is SEO manipulation at scale. By hijacking trusted, high-reputation domains, many of them Brazilian government sites, the operators borrow that reputation to push their own content up the search rankings and hijack the traffic that follows. But the same infrastructure could serve a more dangerous end: the phishing pages impersonate app-download destinations such as Google Play, the Microsoft Store, and Amazon, which leaves the operators one step from pushing malware straight to victims. Infection Flow Figure 1 – Infection chain Initial Access We have not directly observed this group’s initial access, but a revealing artifact surfaced on one of their servers: an exposed open directory hosting an ELF binary written in Go that bundles numerous reconnaissance and scanning plugins. The toolset reads like a complete attack-surface-mapping pipeline for internet-facing targets. The group refers to this agent as “ cluster-asset-mapping ”, or “ cam-agent ” for short. It runs with a handful of flags: default  – long-lived worker session for orchestrated task dispatch f  – foreground mode without logging flog  – enable logging (use with  f ) h  – show help v  – show version Figure 2 – Cam-agent help message The agent carries a configuration that includes: worker_endpoint server_id project agent_token embedded PEM certificates and keys for the server and agent a plugin list report policies It logs to  payload-run.log  under the default directory of  /tmp/asset-scan . The agent reads the JSON report policies to decide how to run its scan. The policies are driven by the following fields: common web ports batch_size retry_count retry_backoff_seconds level Figure 3 – Network scan report policy The agent communicates with its server over gRPC, authenticating with the certificates and keys from its own configuration. It uses many known open-source pentesting tools as modules: dirprobe  – takes URLs and a directory list or profile, sends HTTP requests, and records the status code, response length, and title for each probed path. httpx  – takes URLs, ports, and HTTP options, then collects the status code, response length, title, protocol, TLS details, and banners from each target. naabu  – takes IPs or hostnames, port ranges, and a scan mode, attempts TCP connections across all targets, and marks each port as open, closed, or filtered. nuclei (v3)  – takes URLs, paths, and workflows, executes HTTP/DNS/TCP checks as defined by templates, and emits a structured result for each match (template ID, severity, affected URL, evidence). subfinder  – takes root domains, resolvers, and a depth, then enumerates subdomains via DNS brute force, certificate transparency, and passive sources, returning the discovered subdomains. whatweb  – a Wappalyzer-style fingerprinter that issues HTTP requests to each target and applies rules to identify web servers, frameworks, CMS platforms, JavaScript libraries, and more. Stealth phishing structure Apache Modules The group automates deployment of its malicious Apache module through a Bash installer. The script first confirms it is running as root, then fingerprints the host as either Debian/Ubuntu or CentOS/RedHat and pulls in the matching Apache development packages so the module can be compiled on the victim itself. It downloads the module’s C source,  opsproxy.c , from a hardcoded staging server and, notably, patches the source on the fly to insert a missing macro definition so the code compiles cleanly. This is a small touch that shows the operators built the module to run across a range of victim configurations. Compilation and installation are handled in a single step via Apache’s own  apxs  tooling, which also wires the module into the server’s configuration. What follows is a deliberate effort to hide the intrusion: the script deletes the source and all build artifacts, then timestomps the resulting  .so  and its load-configuration files to match legitimate, pre-existing Apache modules such as  mod_ssl  or  mod_suexec , so the malicious files blend in during a casual review. It then enables the stock proxy, headers, and rewrite modules the malicious module depends on, tests the configuration, and restarts Apache to bring everything live. Throughout, the script’s status messages are written in Chinese and decorated with emoji, a style that may point to AI-assisted development. Figure 4 – Checking the URL by the Apache module The source file,  opsproxy.c , reveals a purpose-built reverse proxy that quietly grafts attacker-controlled content onto a compromised web server. The module registers itself at Apache’s name-translation stage and inspects every incoming request for one of a small set of hardcoded URL prefixes which in our samples,  /wps ,  /bmw , and  /card . When a request matches, the module rewrites it into a reverse-proxy request to a corresponding upstream server hardcoded into the source, silently relaying the visitor to attacker infrastructure while the request still appears, to the outside world, to come from the legitimate compromised domain. To make that relayed content render without interference, the module strips the upstream site’s Content-Security-Policy headers. It replaces them with a deliberately permissive policy that allows inline and dynamically evaluated scripts, third-party assets, and  data:  and  blob:  sources. This removes the restrictions a browser’s CSP normally enforces, allowing injected or externally hosted scripts to execute freely. Figure 5 – CSP stripping so injected scripts can run The module also forwards the original  Host  header and adds standard proxy headers so the upstream sees a convincing request. The effect is a compromised, reputable server acting as a stealthy front door: certain paths transparently serve attacker content, and the browser protections that would ordinarily block foreign scripts are switched off for exactly those paths. Figure 6 – How the compromised .gov site relays attacker content to visitors A second ELF Apache module used by the group disguises itself as a basic filter module while registering request and response hooks that examine visitor headers, URI paths, referrers, and client IPs. It carries a static configuration, decrypts it with RC4, and parses it into two rule types: rule1  – an array of matching rules (path, referrer, or User-Agent, paired with a proxy URL) rule3  – an optional response-filtering or injection configuration Figure 7 – JSON struct example Using a compiled-in regex for  <body.*?>  to locate its injection point, the module expands placeholders such as  {host} ,  {hip} ,  {url} , and  {name} , fetches remote content with libcurl, and writes that content into Apache responses via  ap_rwrite  and bucket manipulation. This gives a remote service control over what selected visitors and crawlers see on the compromised server. This is a behavior consistent with SEO cloaking and content-injection malware. Brazilian infrastructure Fetching the content served from the three upstream IP addresses hard-coded in the proxy module reveals the phishing infrastructure itself. Each address hosts a page impersonating a trusted app-distribution platform, localized in Brazilian Portuguese ( lang="pt-BR" ) and dressed up with fabricated ratings, review counts, and structured  schema.org  metadata to appear legitimate to both users and search-engine crawlers. Figure 8 – Several phishing pages shown by the Apache module. All those IPs lean heavily on Bing’s thumbnail service ( tse-mm.bing.com ) to source imagery, tag their Open Graph and Twitter cards with  @GooglePlay  and  @microsoftstore  handles, and consistently theme around online gambling and sports betting aimed at a Brazilian audience – the actual monetization behind the campaign’s search-manipulation scheme. Tellingly, the pages carry Chinese-language CSS comments (for example a comment translating to “bottom navigation bar — fixed to the bottom on mobile, hidden on desktop”), the same operator fingerprint seen across the group’s server-side tooling. Inspecting the domain used by the second Apache module brought us to a domain called  playfootball[.]info  that has a phishing page similar to the earlier ones. Unlike the earlier upstream samples that pulled assets from Bing thumbnails and a fake CDN, this one loads Google’s real production assets – the actual  gstatic.com  Play Store CSS bundle, Material Icons fonts, and the genuine Google Play logo SVG. Figure 9 – The phishing page used by the second Apache module The most revealing finding from this page is that the app tiles and nav links don’t point to a single server; they point to dozens of real Brazilian domains, the majority of them legitimate  .gov.br  government sites, each serving the attacker’s gambling pages under paths like  /jogos  and  /nova . The compromised institutions span every level of Brazilian government. At the federal level, they include a government ministry and a national public agency. At the state level, victims include a state legislative assembly, state courts of accounts, and a state-owned utility. The largest share, however, is local government: municipal administrations spread across numerous cities and multiple states. A smaller set of commercial  .com.br  sites such as local news outlets, health clinics, and business associations rounds out the victims. Beyond Brazil As we pivoted through the phishing infrastructure, the trail led well beyond Brazil. Several of the IP addresses hosted subdomain and domain generators, giving the operators a fresh supply of domains every day – a rotation scheme built to outpace blocklists and takedowns. Figure 10 – Domain generator used by the group Some of the generated domains pointed to adult-content and gambling sites aimed at a Chinese-speaking audience, tying the infrastructure back to the operators’ origin and their long-running focus on the gambling sector. Figure 11 – A gambling site in Chinese from the domain generator list More telling, we found phishing pages built on the same template as the Brazilian ones, but localized in Vietnamese, Spanish, and English. The Brazilian operation is not a one-off: the same playbook is being adapted for other regions, and the infrastructure is clearly built to scale. Figure 12 – Phishing pages in Vietnamese and English The Attacker’s Arsenal Across these intrusions, the group draws on two kinds of tooling: well-known offensive utilities that any attacker might reach for, such as  netcat ,  fscan , and  pwnkit , and a broad set of custom tools written by the operators themselves: a downloader, several backdoors, a credential stealer, and purpose-built reconnaissance scripts. The sections below focus on that custom toolkit, which is where the group’s tradecraft shows. DownPro A downloader written in Go, referred to internally as  DownPro . Its job is to pull the rest of the toolkit onto a freshly compromised host and launch it. The binary is driven by a handful of flags, and a telling detail stands out immediately: their help strings are written in both English and Chinese. The flags are: u  – URL of the main backdoor to download id  – URL of the ChUser payload up  – URL of the  unix_updates  payload (the PasswordHarvester) j  – offline URL encryptor mode: it takes a plaintext URL via  u  and outputs the ciphertext to use as the flag value in real runs logs  – where to write logs The values passed to these flags are AES-GCM encrypted with a hardcoded key and Base64-encoded, so the operator supplies pre-encrypted URLs at runtime rather than leaving them in the clear. DownPro  then decides where to drop its payload based on its effective UID, preparing two sets of candidate destination paths: one for root, one for non-root. Running as root, it selects one of: /usr/local/bin/systemd-udevd /usr/local/bin/rsync-tsl /usr/local/bin/tcp-tsl /usr/local/bin/snapd-ext /usr/local/bin/fsck-disk /usr/local/bin/nftables-init These names are chosen to blend into a Linux server environment, either mimicking legitimate system components or looking like ordinary utility and network helpers. Running without root, it instead generates one of two temp-style names designed to pass as routine disk clutter: /tmp/php_sess_<32_hex_chars>  – mimicking a PHP session file /tmp/private-tmp-<5_alnum_chars>  – looking like an ephemeral temp artifact With the destination chosen, it downloads the file from the  -u  URL and executes it with the argument  -si . Figure 13 – DownPro main logic The two optional payloads are handled separately. When the  -id  flag is set,  DownPro  downloads a file to  /usr/bin/chuser , sets its permissions to  0755 , changes its owner to root, and timestomps it to match  /bin/ls  and turning it into a setuid helper that serves as a persistent local privilege-escalation backdoor. When the  -up  flag is set, it downloads a file to  /usr/sbin/unix_updates  and runs it with  -v FuckMe#988 , then strips the setuid bit from  /usr/bin/pkexec . ChUser A simple backdoor that masquerades as a  chuser  utility. It executes commands passed through the  -c  flag, but only after passing one of two activation checks: Remote HTTP activation  – the backdoor builds a  curl  command using the  -x <version>  flag and runs it. Activation succeeds only if the command’s output matches the expected value,  chuser no version . Local MD5-based activation  – the backdoor concatenates a user-supplied secret (from the  -s <secret>  flag) with a hardcoded salt,  FuCkMe# , computes the MD5 of  secret + salt , and compares it against a hardcoded target hash. Activation succeeds only on a match. PasswordHarvester A credential stealer based on  3snake  that monitors newly executed authentication programs, including  sshd ,  sudo ,  su ,  doas ,  ssh ,  ssh-add ,  passwd ,  kinit , and  login . On startup, it sets a clean  PATH  environment variable and installs signal handlers so the daemon can log and exit cleanly. It runs only as root, exiting otherwise, and gates execution behind a covert activation switch: the CRC32 of the  -v  argument must match a hardcoded value. Figure 14: CRC32 gate Once the CRC gate passes, the stealer resolves the host’s name and IPv4 addresses, then daemonizes by forking, calling  umask(0)  so it can freely control file permissions, changing its working directory to  /tmp , and redirecting stdout and stderr to a file. To hide itself, it picks at random from roughly 29 fake process names, such as: [kworker/1:2] [ksoftirqd/0] [watchdog/0] [systemd] [dbus-daemon] [journald] [migration/0] [ksmd] It overwrites the original  argv  with the chosen name and calls  prctl  to change the kernel-visible task name to match. The core logic then opens a netlink socket and subscribes to process events ( PROC_CN_MCAST_LISTEN ). On every process execution or UID change event, it checks whether the process name or command line matches one of the target programs listed above. When a match falls outside the expected path prefixes, it enters the interceptor flow: it attaches to the target with  ptrace , reads the credential buffers, and exfiltrates them to its C2, RC4-encrypted and Base64-encoded. AlphaAgent A modular backdoor written in Go, built to land quietly, blend into a busy host, take orders over an encrypted channel, and hand its operator everything they need to work through a network. On launch, AlphaAgent first checks whether it was invoked to finish an upgrade, so an in-progress self-update can complete cleanly. It then parses its command-line flags, validates its configured role and transport, and generates a Device ID from either the victim’s MAC address or the username combined with a hardcoded salt ( e*f#1%0d$6&5=6 ). After checking its debug flags ( DEBUG ,  VERBOSE , or neither), it decrypts its configuration strings using AES-GCM with a hardcoded key. Figure 19 – Device ID generation The configuration holds the region blocklist, the transport role and mode, the C2 domain, the TLS SNI camouflage value used for the certificates, and the directory, filename, and loader names for the rootkit. With its configuration in hand, the agent goes to ground. It renames its own process to pass as a kernel thread or a system daemon, choosing the disguise from its configuration profile and applying it by rewriting  argv[0]  or calling  prctl . The profiles are: aws  →  /usr/sbin/amazon-master  or  /usr/local/sbin/amazon-proxy google  →  /usr/bin/google_user_agent  or  /usr/bin/google_proxy_agent aliyun  →  rsyslogd general  → one of a set of kernel-thread-style names: "dbus-daemon -n%d" "scsi_eh_%d" "[migration/%d]" "[cpuhp/%d]" "[kworker/u%d:1]" "[watchdog/%d]" "[kswapd%d]" When not running as root, it falls back to  php-fpm: pool www  or  nginx: worker process . AlphaAgent then detaches into the background and writes a PID lock file under an innocuous path so that only one copy runs. It sleeps for a randomized interval which is long enough to outlast a quick sandbox detonation, and checks where it is running: if the host’s country matches the operators’ blocklist (China, in the samples we analyzed), the agent simply exits. Only after clearing that geofence does it enter its connect-and-retry loop and reach out to the server. Finally, if the  -r  flag is set at execution, AlphaAgent checks whether the rootkit’s kernel module is already loaded. If it is not, the agent installs it; the rootkit ships embedded inside the binary via Go’s  embed.FS  API. In all the samples we analyzed, we haven’t found any rootkits, only placeholders. Once connected, the agent enrolls, starts a heartbeat, and subscribes for jobs. How it talks to its server is a build-time choice, and each option is designed to look like something benign. The primary channel is  gRPC over HTTPS . The agent’s gRPC transport is built as a publish/subscribe service. The agent subscribes to receive jobs and publishes results back, and on top of that base, it opens dedicated streams for each interactive function rather than multiplexing everything through one pipe. There are separate streams for the web terminal, for uploads, for downloads, and for keepalive pings, and each exists in two directions an operator-facing set and an agent-facing set. That separation keeps a live terminal session responsive while a large file transfer runs in parallel. Three design choices make this channel hard to spot on the wire: uTLS fingerprint mimicry.  The agent uses a library that forges the TLS handshake of a real browser, so fingerprint-based detection (JA3/JA4-style) sees a normal Chrome-like client, not a Go program. Google and Cloudflare camouflage.  It presents  api.google.com  as its server name, serves a  .google.com  certificate, and dresses its HTTPS heartbeats as Google traffic with decoy cookies ( NID ,  SID , and similar) plus a custom proof scheme carried in Cloudflare-style parameters ( _cf_auth_ts ,  _cf_auth_nonce ,  _cf_auth_method ). The heartbeat side exposes handler paths like  /agent/heartbeat  and  /notifications/v1/push  to complete the illusion of a Google notification service. Encryption beneath the encryption.  Job and result messages are themselves AES-GCM encrypted before they travel inside the TLS session. Even an analyst who terminates the TLS still faces an encrypted payload. The Message fields of the communication: Message Message field 1: string cid (label=optional) - connection ID field 2: string mid (label=optional) - Message ID field 3: int32 command (label=optional) - specific command to run field 4: bytes data (label=optional) - data for command field 5: string topic (label=optional) - channel name field 6: bytes encrypted_data (label=optional) - encrypted payload field 7: string sid (label=optional) - stream ID field 8: string file_name (label=optional) - if there is a file field 9: string file_action (label=optional) - can be upload / download / delete / list The alternative channel is DNS. Here the same commands travel inside DNS queries: each job is encrypted, Base32-encoded, and split across DNS labels, then exchanged as TXT-style traffic on port 53. Many environments scrutinize outbound web sessions but wave DNS through ,  which is exactly the point. A separate variant of the toolkit keeps things simpler still, tunneling its protocol over a plain HTTP connection with certificate checks disabled. The alternative channel is DNS. Here the same commands travel inside DNS queries: each job is encrypted, Base32-encoded, and split across DNS labels, then exchanged as TXT-style traffic on port 53. Many environments scrutinize outbound web sessions but wave DNS through which is exactly the point. A separate variant of the toolkit keeps things simpler still, tunneling its protocol over a plain HTTP connection with certificate checks disabled. Whichever channel it uses, the agent bootstraps through public DoH and GeoIP providers such as Cloudflare, Google, ipinfo, and others, both to resolve its server and to run the geofence check described above. At the center of the agent is a single job dispatcher. The server sends a numbered command; the dispatcher routes it to the matching handler. That design keeps the protocol compact and makes the feature set easy to summarize. The sections below cover the ones that matter most. Remote shell and interactive terminal  – The workhorse is remote command execution. A shell job is joined into a single string and run through  /bin/sh -c , and the combined output is captured and returned to the operator. The agent takes care to keep this quiet. It sets  HISTFILE=/dev/null  so commands leave no shell history behind. For interactive work, the agent goes beyond one-shot commands. It can allocate a real pseudo-terminal, launch a shell inside it, and stream that terminal to the operator as a browser-based “webtty” session. This gives an attacker a live, interactive shell with full terminal behavior, not just fire-and-forget commands, which is what you want for hands-on-keyboard operations. File Operations  – File handling is complete in both directions. The agent can download files to the host and upload files from it, with both direct and streamed transfer paths for larger data transfers. Alongside transfer, a file browser lets the operator list directories and walk the filesystem interactively before deciding what to take. Together, these turn the backdoor into a remote file manager for the compromised host. Tunneling and pivoting –  This is where the agent shows its intent to move laterally. It bundles a SOCKS5 proxy, a yamux-based multiplexer, and a Ligolo-style relay, turning the compromised host into a pivot point for the operators’ traffic. A dedicated relay mode lets the agent listen for inbound connections and forward them, so one foothold can open a path into the rest of an internal network. In the tunneling paths, certificate verification is deliberately turned off to keep the relay flexible. Relay Tunneling  – AlphaAgent can also be deployed not as an implant but as a  relay node . The agent validates a configured role at startup, and, in its tunnel-edge role, starts a listener and forwards traffic upstream to the command-and-control server on a different port, preserving the same gRPC streams. It uses its own embedded node token to identify itself in this mode. In other words, the operators can seed both endpoints – victims that call home and relay nodes that concentrate and forward that traffic – from one codebase. One build even carries a tag pointing to a specific tunnel geography ( [dns-hktun / Hong Kong] ), suggesting the relay tier is planned around location. Discovery and collection –  The reconnaissance is aimed squarely at spreading. Beyond a standard host and network inventory: hostname, users, running services, active network connections, interface addresses, and virtualization hints, the agent reads login history from  wtmp ,  utmp , and the system authentication logs, and enumerates current SSH sessions. It can then archive a victim’s  .ssh  directory and  .bash_history  into a compressed bundle for exfiltration. Read who logged in, grab their keys and history, and use the tunnel to reach the next host: the collection features are built to feed lateral movement, not just to profile a single machine. Worth flagging: the host inventory the agent sends home includes a  virtualization role  field, meaning the agent reports back whether it believes it is running inside a virtual machine or sandbox. That gives the operators a chance to abandon or lie low on analysis systems before doing anything noisy. AI Plugin  – The newest build we found, introduces something the earlier versions do not have: an AI plugin execution path. The evidence is currently limited to internal strings. The agent logs executing AI plugins when it runs one and recovers from failures through an AI plugin panic handler, so we can confirm the capability exists and is guarded like a first-class feature, but the sample does not reveal what the plugin is or does. In the code AlphaAgent gets scripts probably written by an AI orchestrator on the server side named “ ai_plugin_%s.sh ”, runs them and sends the result to the C2. Evasions  – The agent invests heavily in remaining unseen. It renames its process to impersonate legitimate kernel threads and services entries like  [kworker/...] ,  [kswapd...] ,  nginx: worker process , or  rsyslogd  and overwrites its own command-line arguments so tools that read them see the disguise too. It suppresses its own output to  /dev/null  and detaches as a daemon. Some builds go further and hide the process outright. On command, the agent can bind-mount over its own  /proc  entry, making itself invisible to anything that reads the process table – a lightweight but effective trick that needs no kernel module. Other builds do carry a kernel-module component, controlled through custom device commands, that hides processes and network connections at the kernel level and can stage an additional loader fetched from the operator. The encrypted configuration and the traffic camouflage described earlier round out an evasion posture that spans disk, process table, and network. One variant is packaged to defeat analysis itself. It is wrapped in a protector that strips the file’s structure, unpacks the real payload only in memory, obfuscates its internals, and watches for a debugger, popping a decoy error and exiting the moment it detects one. Same feature set underneath, hardened against the analyst. The full list of commands: Command IDArgsDescription2server parametersgRPC tunnel4server parametersSocksProxy (using Ligolo-ng)8command stringshell command execution10path, recursivefile browser / directory listing12processname, argv_nameprocess name spoofing14strings of several commandsMulti command AUTOSTART16connection hide + remote install + streaming upload18Install new Rootkit20Uninstall rootkit22unmount process –  CommandRunUNINSTALL 24Http based file transfer26gRPC file upload28gRPC file download30Tun socks relay start32Tun socks relay stop38Hide process via bind mount40Get SSH and bash history42System information collector44Registration acknowledgement46AI plugin execution48Agent upgrade oRAT oRAT is a Go-based Linux remote access trojan built for full remote administration of a compromised host. It starts with decrypting the configuration baked into the binary that contains: the C2 address, the install paths, the process disguise, and the hiding flags all live inside one encrypted blob and are only unpacked in memory. Unless told to skip it, the agent then runs its preparation routine, and this is where most of the damage is done before any traffic leaves the box. It configures logging to  /dev/null  by default, daemonizes, disables SELinux enforcement ( setenforce 0 ), installs itself to a persistent location, registers a service, writes a GUID, takes a file lock so only one copy runs, deletes its original on-disk copy if it was relocated, and optionally hides its own process. Only after all of that does it enter its main loop of communication. The agent’s communication routine supports three transports, selected by config: tcp  – a raw TCP connection stcp  – TLS over TCP sudp  – QUIC over UDP, using the quic-go library On top of whichever transport it picks, oRAT layers a multiplexed session and speaks HTTP through it. It uses a standard Go HTTP client, but rewrites the client’s dialer so every request is carried inside the established oRAT session instead of hitting the network directly. The agent registers with the server by posting a join request to  /join , then serves operator commands as REST-style routes over that same tunnel. Because oRAT exposes its capabilities as HTTP routes, its feature set reads almost like API documentation. The operator API includes: RouteCapability /agent/info Report host details (distribution, kernel, and more) /agent/ping Liveness check /agent/exec Run an operator-supplied command /agent/upload Write an uploaded file to a chosen path /agent/download Retrieve a file from the host /agent/screenshot Capture and return a screen image /agent/zip  ·  /agent/unzip Archive or extract chosen paths /agent/portscan Scan hosts and ports from the victim /agent/proxy Open a SOCKS proxy through the host /agent/net Forward a raw TCP connection to any target /agent/ssh Reach an embedded SSH / SFTP server /agent/upgrade Replace the running binary /agent/kill-self Delete the agent and exit oRAT offers two paths to run commands, and the second is the more interesting. The direct path is a command route that hands operator input to  sh -c  and returns the output, standard RAT behavior. The richer path is a fully  embedded SSH server . oRAT builds its own SSH service into the agent, complete with a hardcoded RSA host key, password authentication, port-forwarding, and an SFTP handler. When an operator connects, the agent spawns an interactive shell: trying  zsh , then  bash , then  sh  with proper pseudo-terminal handling. In practice, the operator gets a real SSH session and SFTP file access on the target, tunneled through the C2 channel rather than exposed on a listening port. oRAT’s persistence is quiet and well chosen. It installs itself to  /usr/local/bin/xtables-addons  and registers a systemd service named  xtables-addons , wired into the standard multi-user target so it starts on boot as root.  xtables-addons  is a real netfilter/iptables extension package, so an administrator glancing at the process list or the service table sees what looks like legitimate firewall tooling. If the agent lacks the privileges for a system-wide install, it falls back to per-user persistence through a user service and a cron entry. It also hides its identity in an unexpected place. The agent stores its GUID by appending a  # GUID: <uuid>  comment line to  /etc/protocols , a legitimate system file no one thinks to check. Its lock file sits at  /tmp/.lock . The evasion posture is layered and Linux-native: Process masquerade.  The agent sets its process name to  sshd: root@pts/0 , so it reads in the process table as an interactive root SSH session. One build reinforces this by spoofing its executable path as  /usr/sbin/sshd . Procfs hiding.  When its mount mode is enabled, the agent bind-mounts over its own  /proc/<pid>  entry, disrupting inspection of the running process through the proc filesystem. Silent by default.  Logging goes to  /dev/null  unless a specific debug environment variable is set. Together, these span the process table, the filesystem, the security policy, and the kernel’s view of the process, a broad effort to make the agent hard to notice and harder to inspect. BruteForcer An SSH credential-checking and brute-force utility. It reads target IP addresses ( -f  flag), usernames ( -u  flag), passwords ( -p  flag), or pre-combined  user:pass  pairs ( -up  flag) from operator-supplied files, then attempts concurrent SSH logins against each target. Successful credentials are printed and appended in plaintext to a local results file,  res.txt . The binary has no hardcoded C2 infrastructure or persistence mechanism and its sole purpose is credential access against remote SSH services. Recon Scripts In some of the attacks we observed a number of Bash scripts with Chinese-language comments used by the attackers. The first,  info.sh , proceeds in four stages. It first pulls recent login activity to profile who uses the box. It then walks every user’s home directory, including root’s, to inventory  .ssh  folders, flag any files containing private keys, and comb  .bash_history  for sensitive commands involving SSH, SCP, database clients, cloud tooling, credentials, and  kubectl , a fast way to harvest reusable secrets and understand the victim’s workflows. The third stage is the most refined: a storage analysis that hunts for remote network mounts (NFS, CIFS/Samba, WebDAV, cloud FUSE) and Docker volumes while deliberately filtering out overlay, tmpfs, and container-ID noise, so the operator sees only genuine lateral-movement targets rather than local container clutter – a sign the author iterated on the tool to cut false positives. Finally, it gathers classic lateral-movement intelligence:  /etc/hosts  entries, local listening TCP ports, and the ARP neighbor table to reveal adjacent hosts on the network. Figure 15 – Third stage of info.sh The second script,  findweb.sh , surveys a compromised host’s web-server landscape and maps out every site it serves. It first detects which web servers are running (Nginx, Apache, or httpd) using several fallback methods, and extends the check to containerized deployments by inspecting Docker for web-server images and any containers publishing ports 80 or 443 to the host. Where possible, it reports the ports each server listens on. It then parses the server configurations directly: for Nginx it walks the common configuration directories, resolving symbolic links and de-duplicating by real path, then extracts each virtual host’s domain ( server_name ), web root, and any  proxy_pass  upstreams; for Apache and httpd it does the equivalent, pulling  DocumentRoot ,  ServerName , and  ServerAlias  from every  VirtualHost  block across the standard Debian, RedHat, and common control-panel configuration paths. The result is a concise inventory of every domain hosted on the machine, where each site’s files live on disk, and where any existing reverse-proxy rules already point. In the context of this campaign, that inventory is exactly what an operator needs to weaponize a compromised server: it reveals which trusted domains are available to abuse, the exact web roots to plant content in, and where to graft the malicious proxy module so that attacker pages are served under a legitimate site’s name. Attribution and links to prior work We assess with medium-to-high confidence that  Gambling Goblin  is tied to  Earth Berberoka –  a Chinese-speaking threat cluster first documented by  Trend Micro  in 2022. Earth Berberoka is known for targeting online gambling platforms that serve Chinese-speaking users and operators, and for working across Windows, Linux, and macOS with a mix of aged commodity RATs and purpose-built tooling. Our assessment rests on three independent overlaps: the malware, the operator artifacts, and the network infrastructure. Tooling.  The group’s use of oRAT is the clearest link. oRAT was tied to Earth Berberoka in 2022, and the variant we analyzed shares the same  orat/cmd/agent  codebase and REST-style operator routes. The connection extends to the group’s custom malware: one of the AlphaAgent samples we recovered was uploaded in the same archive as other tools previously attributed to Earth Berberoka, placing AlphaAgent directly alongside the group’s known toolset rather than merely resembling it. Operator artifacts.  The focus on the online gambling sector and the Chinese-language strings scattered across this campaign’s tooling (dual-language flag descriptions, Chinese script comments, and Chinese-language page artifacts) align with operator fingerprints seen in the group’s past campaigns. Infrastructure.  The group has a documented habit of registering domains that impersonate trusted platforms. Trend Micro reported  github[.]wiki  as an Earth Berberoka domain while the infrastructure behind Gambling Goblin follows the same playbook: lookalike domains such as  github[.]la  and  gitlab[.]bet  closely mirror that tradecraft. Reinforcing the link, many of the C2 servers in this campaign are hosted on the same Amazon ASN ( AS16509 ) the group has relied on before. Conclusion This campaign marks a shift in who targets Brazil, and why. For years, the threats facing Brazilian users came mostly from home grown banking trojan crews. Brazil is a natural target for this kind of operator. It has become one of the world’s fastest-growing online-betting markets, with a vast base of mobile users accustomed to installing apps on the spot, which is exactly the audience a gambling-driven fraud operation wants to reach. For a Chinese-speaking group that has spent a decade monetizing the gambling sector, the money now runs through Brazil, and the infrastructure to exploit it is often trusted but under-secured. A vast base of mobile users conditioned to install apps on sight, and a sprawl of trusted but under-secured web servers, most of them on government  .gov.br  domains whose search reputation is exactly what a large-scale SEO-fraud operation needs. Compromise those servers, graft on a malicious Apache module, and the attacker turns a nation’s legitimate infrastructure into a distribution network for gambling pages and fake app stores. That is the notable part: this is not opportunistic crime but patient, industrialized abuse of reputation, and it is run with espionage-grade Linux tooling in the service of financially motivated fraud, blurring the line between cybercrime and APT. We expect the operation to grow rather than fade. The same infrastructure that inflates search rankings today is one configuration change away from serving malware tomorrow: the phishing pages already impersonate Google Play, the Microsoft Store, and Amazon, putting the operators a single step from pushing malicious apps straight to Brazilian victims. The Vietnamese, Spanish, and English pages we uncovered show the model is being exported, and the daily domain generators show it is built to scale. Countries should expect more of this, aimed higher, not only at customers and banking credentials, but at the government institutions whose domains lend the campaign its trust. None of it depends on novel exploits. It runs on unpatched internet-facing services, weak SSH credentials, and Apache modules that no one thinks to watch. If organizations, and public-sector operators in particular, do not close those gaps – patching exposed services, auditing Apache and SSH configurations, and hunting for rogue modules and masqueraded processes, then this actor and the wider wave of global cybercrime it represents, will keep finding an open door. IOCs Hashes: 232ef6be134c2b7c14648aa193daf7e23e987477b8a40150dd77883947fdf017 088d0742a667f1acfc83edb94671a10b951f6745badec6d5c754ef594dddf815 88544d36beb6dc621c9376806836d0ad109ece64b589605d5674e0c86313d1c0 9d3085eac9a59a94f0473db5ec0173def8777d2f794da281fb1749389ae33cdb 263c14e84398339b25cd3e59da7e108340306fdbb8112bbe7dc0f07a71eb8a31 12af9d95c44e20a375148c25f8a2978a62ee95489134654c3537ccfb2d42120d 5af1bec4635e52da4909bf744ea4b7e4483ec944241218855212f4a9e3d48611 e8bb763bd10e727228ca9a8e3e6cf10bf4de4639b6be680a3abfb181a0adc052 fa7fc029ac13af2f3880151e9c408e9afadeba7b2cff01659806fb7c3c83288d c3c09fe219e10808f053e580628aeb87b1f00fc683c810aa828905fe03cda98f 2567d6b42dac97a391217ad22ee375f504d541940d3fbb9436a3f5e9bb23ab91 1829efbf7946e1a958779a3e7f1e50ca63fe61c6a2ddc177c14a7b0c5e10020a f025520d648c7799ca5bed4a9be5bee14ac33be1f1e9b20c090c8c6319404fcf 5a11ed7931fb6358846e0f3c8d69921f43f8ccade5937fc41e5c262cc49f82e8 0d4a28d5cf7b99f11ffe972abd0284d9e35b6858eeb288532a55633b3e29f9c7 5f6d112637545a2e8c1a9f260c39698852c7a22e83db5ccfc99b99d9f6274710 c4d2efa57eef0c5defc4ca708ebe35832f8b543cf764beebef56fef6d36d4f69 c3c6ab58514cd13638cf049332186ef6d4ec7b256913edb1cd66a19437608882 582ecca146a6aef478706e4b2774d6115a9220a18d1db8f92ee54a5118ecebd9 3a8f464f1f2b5c38173e2a96f95a690af327d85c13c04d37cf0a91893d487bdb 02f5e07dd4c97a3de48cc886f46dad35443f1c221a352630e2c7787806ee21b6 16d35a725819142d2bd5bc0949dc518d344d6f63626a517e67fcba7322eb3844 a71498bfffae8ac694356b3f2436820b396946c9e71c8915e282c1b2fdba4162 d138d5f4fbc77650bc3be1cbf8fbd0ee292aa30eed5feec1ea7ba02e57da932b 44373953431d7570d9585c91377dbe8b6527ccc00662d249f383b003b68b459f 45b9382d7e91a4178b47c908b9b5f6884de7c5a1ef849fbf01d6c23d06d81b88 1eb40363a64e0cad15e340af476d106ccf57ebb6662c1389da1347429ee68c9c fc789397742aee60b01292b071f79b4165981c31aa431eb1577a47c5911381c3 adbee84e9a43949b0a816f052ffb3c0b7855e078b985fea95532158c3b9389bc 0f26e1ba39ddd1f0a7e6f72bd8c4e02a5f0140de72eeda9fe5ab56402821e31e ab7d531d298f0d77bc7bbbdc36f4f8a1732ceca90ff60e3f225a99b9b10f334e ac99754357bd4a69c1de576977e0ee19c7354f29f7f52a9893b7a60f9c2f5248 94aa88ff6222583b2a5b791ddd655837787e31f59483ed91f860857d3399b84a 3ad35ea116b2c0855c13459a04699318b3944762385e8a47144f1d03b48f0bb1 0611c153bf8b8561ef53f2a5ba1413115bdc0e4554e0c22cf9641bd8845db03e 114824bccfafcbb42040f119fdcd3ec48f54eb154ffee6676d06986cba2b0af0 297c53d935c501864e15fe7abcfdafed83df9aafdf241094604ae405529c5eb7 0963c0034a5e0665729d686d50c5375948c4a684c56770adb13d24ff5df8013d 749784fb7846bb3b52dd8c2f660b53d95d5df30387b87b65b584ef9cc781ae52 8495598b1fec814d72caf76f1460b132071bb7305335331fed3bac9876c6e40c 98e17fe36ff77106bbbb9a04f3e00004bf872b88aab22438076966913ea83322 bcd7e5964630c34f06a43e48d696d99d7abae6b679509ad839ffa5179a972838 24f7296ac5ce844678c5f7470eaf64b28e870108ca06851c8f66a27a52003f12 2de964314a8aacc40897140f6fe21d268e24503a69f9821177e31bca7b1e4035 52863d36a216a86b2f90914db2d9229cba7ea317ab5ee9a678cb229087f04611 9d513a419bf129a42017b29eb7d084451a4f34be0828f6871439ec79f7f9b5fb d478f867512e18d839180ceafc980c8fb26c3aa7d1c9e96d054819c81afef6f4 b88a7f3288bdf4b97d75dad4e47e5cb3d4e0962b12674a08e32e5f96e762e877 f4aceaf5c0740093f8040f5e0f29c7582a1bd7ab2bca628d162fb45c29045063 2305ae23ea350e31b05b9f071d315ee60c5a88e96ce11be8ff9db16314a6197c 99b5404df81992cad104dd242bc736d75fd6c58af34dc1a75a8ee3c5e1784fa4 85b5e95cbb5103202abebf8f84b91a286994e61b33ddef53355ab0df2a2b6d9a cff25a9c84c893e32a9a75c1dae385934cf917f709efa11172a53ea2337fa109 154c977a113ff4d94ff2f29f7b93a8d0bd6ad8e67a820c09505117f5d386fd40 67ccc12c0a17dc31388a8c851d076edaaf1213e80398b01d46f5a29b8c7b8b9b e8bc706b0b007d6a122c6b19e87451e550baee793540774db13b9a08803ed76a f32dfbe4a2c11a975d735297bf76f6497ce9f5789ab8eaaef3fdd182c2f1f7b1 c59ebe5cf45935c7b5f91b5936fe2c8a5feb7ca161e40ca4e3fb93e447373fa6 3537bfeaf2c18feafeaf773700a88118fd50979d97f2c42c7e34ba6c9aa62820 2949f0b16b83b35dc8a3dfa11815b9516403e3997e13100e7b86f3bb81f6c283 0e7c96a22e3612c68866a8693cc583df95972d3444978ce163c024a45682133a 7d9f5eb3f704607e6f63681842f48071cc58f2f2e63b16b64a49440cb4b9e6e3 8a64d368ce14c5a1f5e775714bcc02f080d0541360743bb4235e0d640f1787b1 36cf87fe2e29cc8b0fd84fce91d70e62a4c4d2fc5f9650dc37440d629ae61b8f 090e886e5605255ad5708e1f27aecc54319de835abd28853e54182981410707e fa7d8c44a0ecb5ec40832d0d2cfe22c47879317177eae88d178e156f1c8d61a3 d948b486c740b66642a5ae29dc1cb80da703ad40296bcda34a1b27216b63a5cd 612fe3a3ace706725aa5415a1cd1cf18548627b4b40636c5443cb770def30b4c 96488c59287889fcd3b9952ec78b78914fabb901c8b61a7354552439170ed148 Domains: rb[.]aliyuntsl[.]com br[.]team-c2[.]com hwlocal[.]team-hw[.]com br[.]team-hw[.]com data[.]mirrors-inc[.]com team-hw[.]com update[.]team-c2[.]com devops[.]aliyuntsl[.]com bageyi[.]kernel-lib[.]com 8yiu[.]kernel-lib[.]com dnslog[.]kernel-lib[.]com js[.]ai-jquery[.]com api[.]onlinevrgame[.]com file[.]ijjjst23m[.]com kerneltty[.]com 80[.]443[.]team up[.]443[.]team 404[.]443[.]team data[.]windows-update-cdn[.]com microsoft-azure-loadbalance[.]com update[.]aliyun[.]la api[.]gitlab[.]bet github[.]la update[.]opentls2[.]com IPs: 154[.]84[.]62[.]160 154[.]84[.]62[.]128 154[.]84[.]62[.]149 154[.]84[.]62[.]145 15[.]228[.]251[.]82 56[.]124[.]87[.]60 18[.]229[.]255[.]14 18[.]166[.]208[.]57 18[.]228[.]136[.]28 43[.]198[.]248[.]193 43[.]199[.]133[.]195 18[.]166[.]243[.]179 18[.]164[.]116[.]24 13[.]203[.]9[.]172 43[.]198[.]30[.]170 18[.]162[.]210[.]53 56[.]125[.]218[.]234 18[.]228[.]195[.]216 56[.]124[.]49[.]89 54[.]207[.]196[.]189 165[.]22[.]101[.]200 172[.]80[.]8[.]202 104[.]206[.]37[.]134 108[.]187[.]28[.]158 202[.]146[.]222[.]18 192[.]253[.]229[.]23 16[.]162[.]255[.]92 13[.]250[.]18[.]158 18[.]163[.]182[.]231 204[.]16[.]172[.]106 The post Gaming the system: how a Chinese-speaking actor turned Brazilian government sites into an SEO weapon appeared first on Check Point Research .
research.checkpoint.comSep 2, 2026extracted
Detection blind spots: non-standard file formats in malicious email campaigns | Kaspersky official blog
Threat actors are constantly developing new attack schemes — from OAuth token theft to attacks on AI agents — but the classics never quite leave their playbook. On any given day, an employee may receive malware attached directly to an email, or lying in wait behind a link embedded in an email. Making these attacks succeed still requires a degree of creativity, and in recent years attackers have increasingly adopted exotic file formats. Users don’t perceive these formats as dangerous; more importantly, many EDR and email security solutions skip scanning them entirely. Yet they’ve proven highly effective for deploying malware or harvesting credentials. Below are the file types that may be blind spots in your organization’s detection strategy — despite being observed as used in real-world attacks. Disk images This is the broadest and most dangerous attachment category. A disk image can contain a fully prepared, correctly structured set of files tailored to a wide range of attack scenarios. It mounts as a separate volume (standalone virtual disk), and when doing so often uses tools built into the operating system. The victim doesn’t need to extract anything or create suspicious folders on disk. The most versatile format is ISO, which dates back to the heyday of multimedia CDs. ISO images mount natively on every major OS without additional utilities, whether through simple tools like File Explorer or via the command line interface. This is precisely why threat actors have no hesitation in sending ISO files as email attachments . Somewhat less common are IMG containers, which also mount without additional tooling on macOS or Linux, but require installing a small, free utility such as OSFMount on Windows, or using WSL2 (Windows Subsystem for Linux), which is built into recent Windows versions. A file with identical content may also carry a DD extension. Threat actors also make use of VHD , a virtual disk format native to Windows, which generally works on Linux machines as well (via qemu-nbd or guestmount). On macOS, an additional utility — again, qemu-nbd is a common choice — is required to mount it. Note that on unpatched Windows systems, the victim doesn’t need to take any further action after the disk mounts: CVE-2025-24993 — a vulnerability actively exploited in real-world attacks — triggers attacker code execution immediately upon mounting the image. For completeness’ sake, VMDK, the disk image format used by VMware, is also worth detecting, though it’s largely ineffective in attacks on regular users since every popular OS requires additional software to mount it. All of these image formats can be viewed and unpacked not only with specialized tools, but with standard archive utilities like 7-Zip or RAR. As a result, the odds that the user will fall for the bait are higher than one might hope. In addition to not being a well-known potentially dangerous format, image files give attackers one further advantage: files extracted from disk images on Windows frequently lack the Mark of the Web flag, and therefore can be launched without triggering additional system warnings. There’s one more reason why EPP/EDR solutions must scan virtual machines and disk images: these formats are also used during later stages of an attack. To mask active file-system activity from monitoring tools, ransomware gangs sometimes run the entire encryption process inside a virtual machine deployed on the victim’s computer. The RagnarLocker ransomware strain has used VirtualBox for this purpose, while the CRON#TRAP campaign relied on a QEMU environment. MS Office files No, this isn’t about macro-laced DOC files. Microsoft has grown weary enough of this classic attack vector that macros in downloaded documents are now blocked outright , and enabling them requires considerable effort from the user. But Office relies on dozens of file formats, and some of the less common ones still occasionally give attackers an edge. Less familiar to both users and security solutions are OneNote files (.one). These are essentially simple notes, but they can carry embedded attachments, including not just images and links, but VBS/WSF/BAT scripts as well. Within the note, an attachment normally displays as an icon, but attackers overlay it with a picture showing a message with a “View” button. Another Office format popular with attackers is the Excel add-in. These files use the .xll extension but are, in effect, full-fledged Windows dynamic-link libraries (DLLs), and therefore may have extensive functionality. Victims receive a malicious email with what looks like an invoice; the icon suggests that the file will open in Excel. Ignoring the security warning may result in an infostealer infection . SVG “graphics” The description of the SVG (Scalable Vector Graphics) format sounds entirely innocuous. Indeed, 99% of SVG files are logos and interface icons. But unlike PNG or JPG, SVG files are fundamentally XML documents, and beyond points, lines and fills they can contain JavaScript. In terms of malicious potential, SVG is not far behind a full web page. In real-world attacks , SVG files can redirect a user to a phishing page immediately upon opening, or render the phishing page directly by unpacking a Base64-encoded block into full HTML. SVG files pose a distinct risk to corporate portals that accept user file uploads. If a portal’s Content Security Policy (CSP) isn’t sufficiently restrictive, and lets someone upload a malicious SVG file, the embedded JavaScript can steal cookies from the page, inject unauthorized content, and carry out similar attacks. Polyglot files Polyglot file formats are less exotic in and of themselves, but the files carry more than meets the eye. They’re called polyglots because attackers construct a file that can be validly interpreted in multiple ways: for example, it can be a valid ZIP archive and a valid executable at the same time. The purpose is purely to evade detection by security solutions and deceive the user. We’ve covered polyglots in detail in a separate blog post . The clear standout in our roundup is a malicious campaign distributing the IcedID infostealer . Victims receive emails with a ZIP attachment, which unpacks into an ISO disk image. That further unpacks into a CHM file (the Windows Help format) that’s also correctly processed as an mshta (Microsoft HTML Application host) application, which then downloads the primary malware payload. Defending against exotic files These attacks rely on the assumption that security solutions either don’t scan unusual file formats, or scan them only superficially. Preventing the threat starts with not operating on that assumption with regard to your own infrastructure: Configure EDR , web, and email filters to scan all of the file formats described above. Process archives and disk images with the same rigor as you would apply to executables. Detonate potentially dangerous file types in a sandbox, and configure recursive unpacking of nested formats through to the end of the chain: ZIP → ISO → CHM. Where feasible, quarantine all file formats anomalous for email — disk images in particular. Build detection rules for anomalous usage patterns that involve exotic files. For example, unusually small disk images are rare and are therefore worth investigating. Review the technical documentation of your security solutions to confirm that complex formats are detected through deep structural parsing rather than magic-byte checks alone. Deploy behavioral detection capable of flagging anomalous execution patterns and legitimate utilities launched from unexpected contexts. The usual suspects here include mshta, git, wscript, hh, and rundll32. SVG files warrant a dedicated policy. Treat SVGs as active content at the email and web perimeter. On corporate portals, enforce a strict CSP, and serve user-uploaded files from a separate subdomain so that a malicious script embedded in an SVG can’t access the session on the main portal.
kaspersky.comAug 28, 2026extracted
Tracking TamperedChef Clusters via Certificate and Code Reuse
This article documents novel activity clusters that have significant overlap with the publicly described threat known as TamperedChef (aka EvilAI). TamperedChef-style malware is trojanized productivity software, such as PDF editors or calendars, that deliver malicious payloads. These campaigns typically employ malicious ads that direct users to sites hosting the applications. While this style of malware shares many similarities in technical operation, installation lures and distribution methods, we do not attribute it to a single author or group. TamperedChef-style malware samples share characteristics with potentially unwanted programs (PUPs) and adware. These include robust mechanisms to remain persistent, and end-user licensing agreements (EULAs) that attempt to legally cover the software's questionable actions. However, TamperedChef-style malware is far more stealthy than PUPs or adware, remaining dormant for weeks to months before activating. This includes continuous command and control (C2) methods enabling adversaries to retrieve additional payloads, such as information stealers, proxy tooling or remote access Trojans (RATs). We have been tracking several campaigns of TamperedChef-style activity starting in 2024, with three distinct clusters: CL-CRI-1089, CL-UNK-1090 and CL-UNK-1110. Between the three clusters of activity, we have identified over 4,000 samples across 100 unique variants. Palo Alto Networks customers are better protected from TamperedChef activity discussed in this article through the following products and services: If you think you might have been compromised or have an urgent matter, contact the Unit 42 Incident Response team. Since early 2024, we have observed a sharp increase in information stealer-style incidents originating from software mimicking legitimate productivity tools (e.g., PDF editors, ZIP file extractors, GIF image makers). Upon deeper inspection, these applications generally contain code that enables the delivery of arbitrary binaries. These features are typically used to deploy stealer malware. In 2025, our telemetry revealed over 100 unique variants of malware masquerading as productivity software. They all contained a malicious component, such as basic RAT capabilities, or delivering adware and infostealers. Due to their legitimate functionality and tendency to remain dormant for long periods of time, these applications often go unnoticed by the victim. They are also commonly downplayed or miscategorized by defenders and security researchers as potentially unwanted programs (PUPs). Because these applications can execute arbitrary code on victims' machines, either directly or indirectly through module loads, these threats are more significant than mere background annoyances or adware. We have been able to track over 4,000 file hashes and 81 unique code signing organisations through several methods, including: Reviewing code-signing certificates of the binaries Analyzing code reuse among the binaries Open-source intelligence (OSINT) on corporate structures for organizations distributing the binaries Leveraging ad transparency platforms to hunt for advertising overlaps that can identify additional organizations distributing the binaries We have identified TamperedChef-style malware campaigns starting in 2023. These malicious productivity application campaigns include AppSuite PDF, Calendaromatic, JustAskJacky and CrystalPDF. The actors behind these campaigns take steps not commonly observed with other adware groups to remain undetected. In some cases, these attackers appear to diversify their revenue streams through more aggressive and malicious activities. This diversification includes deploying infostealers, establishing residential proxies and exhibiting behavior that resembles access brokers. These applications avoid many of the common indicators that users are trained to associate with downloading malicious software, such as: Distributing via well-built, legitimate-looking websites - Without ads (as shown in Figure 1) - Appearing modern and credible - Containing common elements like descriptions, legal terms and contact pages Leveraging unique and contextually relevant domains for each campaign One-click download buttons distributed by large content distribution networks (CDNs) to minimize friction Providing promised functionality with minimal bloat, meaning victims are not likely to suspect anything is amiss Attackers also employ several tricks to avoid detection. These tricks include: Using code signing to increase the apparent legitimacy of the binaries Rebuilding binaries with only minor changes on a frequent basis to minimize the effectiveness of static or hash-based detection - The exact frequency varies, but is typically between one week and one month per rebuild Remaining dormant for periods of weeks to months before retrieving or running malicious components This combination of technical and social masquerading enables these applications to remain undiscovered, unreported and free to operate without resistance for months — if not years — at a time. Adware is a class of software designed to increase the number of ads a user observes. The more ads they observe, the more money for the distributor. This is typically done with some form of browser manipulation or additional free tooling bundled alongside downloads. Adware sits in a middle zone between malware and legitimate software, often employing malware-like tactics to maintain persistence or display more ads to users. The distinction between malware and adware can be so fine that they are indistinguishable from each other when statically analyzed, only becoming clear after misuse occurs. Adware and malware are also often interlinked, with many seemingly legitimate adware developers overstepping into malware territory, either naively or intentionally. Modern adware also walks the line between legal and illegal behavior. EULAs are ways that the groups behind adware and TamperedChef-style malware attempt to protect themselves legally. Examples of this are found on websites distributing TamperedChef-style software, such as one from hxxps[:]//www.crystalpdf[.]com/conditions: “The Additional Services offer users enhanced, tailored features. Be aware that using these services may modify your browser’s new tab settings or installed features, possibly altering your browser configuration.” However, TamperedChef-style programs execute commands remotely, exfiltrate users' credentials and deploy malware without consent. These actions firmly place them in the malware category. The name TamperedChef was initially given to a cluster of activity that included several malicious recipe applications, PDF editors, manuals and search assistant applications. It started to see widespread installation in June 2025, with some evidence suggesting these applications have been in the wild since February 2025. As reporting on malicious productivity apps within the cybersecurity community grew, TamperedChef became a broad, informal term for several productivity software campaigns. These campaigns are likely not all operated by the same group. The confusion in previous reporting is understandable, as many of the actors are leveraging extremely similar tactics, techniques and procedures (TTPs) and lures. The differences only become apparent when observing the infrastructure, code quality and organizations tied to the code signing. It is important to understand these differences to separate the attackers' motivations, capability and risks. We identified and tracked three major clusters of activity that share many of the same operational traits, but we believe these represent three distinct groups. We track the three main activity clusters as CL-CRI-1089, CL-UNK-1090 and CL-UNK-1110. The CL-UNK-1110 cluster is most commonly associated with the TamperedChef alias and includes campaigns distributing applications such as: JustAskJacky GoCookMate RocketPDFPro ManualReaderPro Acronis has researched and reported on this cluster in detail. While this cluster remains active and significant, the primary focus of our analysis will be on the two other clusters, CL-CRI-1089 and CL-UNK-1090. The CL-CRI-1089 cluster has been identified as active since early 2023. It includes several high-profile campaigns distributing applications such as: Calendaromatic DocuFlex AppSuite PDF These campaigns leverage a diverse set of deployment methods and show the most change when it comes to the malware’s techniques and tactics. This group leveraged infrastructure and code-signing certificates related to Ukrainian, Malaysian and British entities, which has remained consistent over the last two years of operation. CL-UNK-1090 is unique in its clear evidence of vertical integration between marketing and malware creation. Similar to other clusters, the group behind this cluster distributes its malware via malicious advertisements (aka malvertisements). A review of public records on corporate structures shows that, unlike the other groups, CL-UNK-1090 operators own both the code-signing companies and the ad agencies distributing the malware. This cluster used primarily Israeli infrastructure and code signing entities. It is responsible for several recent campaigns, including: CrystalPDF Easy2Convert PDF-Ezy We have observed approximately 12,000 unique instances of this fake productivity software across our customer base. Our analysis shows that this threat is global with no significant geographic or sector targeting within the Managed Threat Hunting customer base. The data highlights that while Israel and the U.S. see slightly higher targeting than other countries, TamperedChef-style malware is seen globally in non-negligible volumes. This is consistent across all three clusters, indicating that they all appear to operate globally. Understanding the capability of these threats is crucial to detection, response and disruption. Fortunately, the malware operators have made several design decisions that we can leverage to identify and link large portions of their operations. One unique attribute of the TamperedChef-style malware is that almost all the first-stage binaries are signed with legitimate code-signing certificates. Attackers used code-signing to add stealth to these payloads. However, a lack of proper certificate hygiene allowed us to follow these samples further than any one campaign. We initially identified code signing reuse with the Calendaromatic campaign. This campaign involved a simple Neutralinojs framework-based calendar app, contained in a 7z self-extracting archive (SFX). The calendar app would operate as expected, but it also contained a relatively basic RAT that enabled attackers to collect and install a second-stage payload. This campaign gained some attention due to its novel use of homoglyphs to obfuscate the incoming command strings. The 7zSFX when extracted contains both a calendaromatic-win_x64.exe binary that is essentially just a wrapper for the real bulk of the code, a heavily obfuscated Neutralinojs resource file named resources.neu. Public reporting highlighted that the 7zSFX file was signed by CROWN SKY LLC. Digging further through malware repositories, we identified four total files with the same core behavior of a 7zSFX file containing a calendaromatic-win_x64.exe binary and a resources.neu file. The resources.neu file varied across the samples. However, all appeared to contain similar functionality with differing C2 locations. Of these four samples identified, we identified two unique signers. Samples one and two were signed by CROWN SKY LLC and sample three was signed by MARKET FUSION INNOVATIONS LLC. The final sample was found to not be signed and may not have been deployed widely. Code-signing certificates are considered private material and not commonly shared between entities. A single code base signed by two uniquely authored certificates generally indicates that a single entity or actor is in possession of both code-signing certificates. This can occur for several reasons, including certificate theft, a single entity with ownership of two or more organisations (e.g., shell corporations) or organisations providing code signing as a service. Reviewing sample repositories for evidence of this new signer, we found two additional campaigns that we identified as related to the Calendaromatic operators: PDFPrime and ManualzPDF. Both PDFPrime and ManualzPDF campaigns share striking similarities and likely share a codebase. Similarities between the samples include: The same C2 domain structures Shared code signing dates Shared embedded PDF editors However, these samples are very distinct from the Calendaromatic campaign, sharing no code. This highlights attackers’ preference to abandon codebases upon discovery rather than iterate and evolve. Figure 2 below shows a simplified view of these certificate chains. The PDFPrime and ManualzPDF campaigns have several distinct variants, all with different code signers. Due to the high degree of code overlap, we clustered 34 samples to the PDFPrime/ManualzPDF codebase. We call these samples PixelCheck due to the C2 domains leveraging the format of pixel.toolname[.]com. They represent some of the earliest evidence of the Calendaromatic operator’s activity originating in late 2023. Pivoting through sample repositories to identify other examples of the PixelCheck variant, seven additional signers were identified in the code of related malware: ADVANTAGE WEB MARKETING LLC Europae-Solutio Ltd SP Development and Solution Limited BUZZ BOOST ADVERTISERS LLC ADSMARKETO LLC LLC MATCH-TWO-USERS Monetize forward LLC Tracking these samples via code signing overlaps involves: Identifying the code signers Mapping their certificate chains Pivoting to similar samples Repeating the steps with newly identified signers This iterative approach uncovered an extensive network of seemingly disparate samples, all linked to a single group through certificate ownership. While effective, this discovery method relies on lax operational security. True certificate isolation would prevent expanded identification and limit certificate burning. Reusing code signing across variants also does not appear to be a cost-saving measure, as multiple campaigns often use unique signers rather than reusing a small set of certificates. If cost minimization was the primary goal, we would not see these cases of individual certificate use. Certificate reuse most commonly appears to be a result of poor testing practice, where attackers use previous certificates on early samples of a new campaign before they can procure a dedicated certificate. At the current cost of code-signing certificates, burning more than two certificates per campaign carries heavy financial costs. As a result of this research, we attributed a total of 34 unique code-signing certificates related to the Calendaromatic campaign to the CL-CRI-1089 cluster. Based on the current cost of code-signing certificates, this inefficient approach likely cost the operators over $10,000 in certificate expenses alone. This further highlights the scale of this operation, where this sum is likely considered a reasonable operational cost. Much of the TamperedChef-style malware distribution is via ads, and as such it is subject to ad transparency. Ad transparency is a byproduct of regulation requiring players in the distribution of advertising to provide insights into ad content and owners. Many of the major platforms in the space have their own version of an ad transparency tool or dataset, and investigators can use these to map and track malvertising campaigns. In most cases, ad transparency platforms enable searching either by the advertiser or the site being advertised. While the definition of an advertiser can be complicated, for the most part, the advertiser is the entity that sold or is selling an ad within the platform. This means there is no guarantee that the malware operator and the ad seller are the same or related entities. However, it implies that the malware operator has interacted with the advertiser in some capacity (e.g., exchanging funds or ad details). Advertisers using these advertising marketplaces are held to certain standards by the platforms and must abide by the terms of service, which distribution of malware would typically breach. TamperedChef-style campaigns are different from many other malvertising campaigns, as the malware creators and advertisers are generally vertically integrated. This vertical integration means advertisers also create the malware and, on occasion, sign the code. This direct link between code signers and advertisers implies a strong relationship between malware operators and distributors. This link can provide a starting point to map the wider network distributing this malware. This is particularly evident with activity in CL-UNK-1090 being run by attackers that are clearly well versed in using ad marketplaces to distribute their malware. For CL-UNK-1090, we identified more than 20,000 unique ads deployed over several years via ad transparency platforms. This volume of ads is unlikely to originate from an individual. The OneZip campaign belonging to the CL-UNK-1090 cluster provides a real-world illustration of how tracking these clusters through advertising commonality and agencies works. OneZip is a malicious compression tool with binaries signed by TAU CENTAURI LTD observed in the wild in early 2025. OneZip was distributed via the site onezipapp[.]com (Figure 3 shows the landing page). By leveraging ad transparency platforms, we find that a single advertiser (CANDY TECH LTD) creates and distributes ads for onezipapp[.]com. Based on information from these platforms, CANDY TECH LTD has distributed approximately 4,000 ads that appear related to malicious productivity applications starting in June 2024. Figure 4 below shows an example of the ads distributed. While not the most innovative, attackers have taken care with these ads to consider language, format, logo and branding. This indicates an actor well-versed in the AdTech space. Between June 2024 and December 2024, ad transparency platforms report that CANDY TECH LTD pushed ads for JustConvertFiles, a similar TamperedChef-style campaign. JustConvertFiles is a malicious file conversion tool similar in operation to all other TamperedChef-style samples. JustConvertFiles binaries are signed by B.L.A ASPIRE LTD and PASTEL CONCEPTION LTD, and entities with these names are both observed reusing certificates. These entities appear to be responsible for several other campaigns, including: PDFPilot SwiftNav ShinyPDF FileEase Based on advertising transparency data, we have not observed CANDY TECH LTD representing any campaigns other than TamperedChef-style malware. CANDY TECH LTD is also observed in the malware creation stages, too. Several TamperedChef-style binaries are signed by CANDY TECH LTD or have other links to an entity with this name. These include: ZipMakerPro GifsMakerPro ScreensRecorder RapiDoc (contained a copyright stub with CANDY TECH LTD, but not signed) We then performed the following activities to substantially flesh out CL-UNK-1090 and CL-CRI-1089, and to identify additional campaigns: Leveraging known TamperedChef download URLs Identifying the advertiser Pivoting around the public information on these advertisers These advertising pivots are not without limitations, and many malvertising actors do not have the expertise to set up the AdTech infrastructure, instead relying on established entities for distribution. This makes any sensible linking through public sources much more difficult, as most of the time, the malware advertising only accounts for a small percentage of the advertisers' overall ad presence. In these cases, other methods are likely to be more effective. However, when possible, investigating the distributor can provide more information. The TamperedChef-style malware footprint is large and well-organised, with hundreds of campaigns and large sums of money invested. All TamperedChef certificates are validated by an organization, which means certificate authorities require a corporate entity to fulfill OV/EV requirements to be granted certificates. Certificate issuers impose these validation requirements to aid in maintaining the reputation of signed code. There is a cost, of both money and time, for adversaries to establish a corporation for the sole purpose of signing code. Corporate structures tend to leave traces, particularly in countries where data is publicly available. This opens new avenues for discovery. OSINT sources such as private and government-run corporate search engines can be used to gain rapid insights into corporate entities. Our primary focus areas when tracking code-signing entities were: Co-location, especially in residential dwellings Companies with a handful of employees and minimal presence, especially when owned by much larger corporations, can indicate possible shell corporations Shared ownership structures, particularly when shared ownership is by an individual and not a corporate entity History of company renames (especially renames that are potentially aligned with malware campaigns) With the CL-UNK-1090 cluster, we can use CANDY TECH LTD as an example again. Ad transparency data indicates that CANDY TECH LTD is registered in Israel. Leveraging Israeli company search engines, we found CANDY TECH LTD with a listed phone number, website, address and ownership structure. Figure 5 below shows the webpage for CANDY TECH LTD. From public records, Zizik with me is the director of CANDY TECH LTD and Fairark Systems Ltd. consists of option holders for the company. Zizik with me and Fairark Systems Ltd. are listed as having sole ownership stakes in several companies in Israel, such as: AMARYLLIS SIGNAL LTD TAU CENTAURI LTD RED ROOT LTD BITTERN SKY LTD TOGO NETWORKS LTD The list of companies that we mined from the Zizik with me and Fairark Systems Ltd. ownership structures — as well as some minor variations and co-location checks — match the names of companies that signed significant volumes of TamperedChef-style code. With high confidence, we believe these ownership structures link all cases to a single group. Additionally, many of these companies have undergone several name changes in the past three years. Many of the old names match names that were used to sign TamperedChef-style malware. Fairark Systems Ltd. is the registered name of FireArc, an Israeli advertising company. It states it creates games, connected TV applications, eCommerce solutions and, notably, utility applications. Figure 6 shows this statement on its website. Additionally, the RapiDoc campaign created by CANDY TECH LTD has a program database (PDB) (D:\!Work\Clients\ \Projects\RapiDoc\SrcForTests\RapiDoc\x64\Release\RapiDoc\RapiDoc.pdb). This could have been left by mistake in the RapiDoc binaries installed during execution. PDBs are created during the build process for binaries and contain useful symbol and debug information. Binaries that are productionized tend to remove the PDB, as it can provide reverse engineers a head start when analyzing a binary, which is not desirable for either legitimate software or malware. PDBs, where applicable, were for the most part removed from other TamperedChef-style samples, indicating that this was likely an error. The SHA256 hashes for the binaries containing the PDB are: 248de1470771904462c91f146074e49b3d7416844ec143ade53f4ac0487fdb44 2231bfa7c7bd4a8ff12568074f83de8e4ec95c226230cccc6616a1a4416de268 Leveraging several linking methods, we broadly identified significant portions of these activity clusters’ operations, mapping several networks of TamperedChef-style malware. While this may not represent their entire infrastructure, it highlights the pervasive nature of this threat. We supply all identified samples, domains, signers and any other relevant details in the Indicators of Compromise section. Using Calendaromatic as a starting point, we mapped out the CL-CRI-1089 cluster to include 34 unique code-signing entities. Our primary method of identification was code and certificate reuse. We observed some evidence of shared corporate addresses with code signers. However, generally, each entity was separately created and operated. The CL-CRI-1089 cluster included malvertisements generated through self-created and likely dedicated companies. This cluster did not appear to cross-contaminate advertising entities with code-signing entities. This cluster primarily leveraged companies based out of Ukraine, Malaysia, Singapore, the U.S. and the UK to perform operations. In cases where the owner's place of birth was recorded by the UK government, all owners were of Ukrainian origin. We identified over 3,300 samples related to CL-CRI-1089 across Palo Alto Networks and public sample databases, with the vast majority related to productivity software. We mapped out CL-UNK-1090 primarily through a combination of real-world incidents, OSINT on the FireArc corporate structures and advertising network links. Certificate and code reuse were present but formed less of a basis for discovery. We found CL-UNK-1090 used 39 Israeli corporations for certificate generation. This cluster included changed organization names to mine these structures for multiple certificates, so the real number of organizations is likely less than 39. We identified approximately 750 samples related to CL-UNK-1090, all with productivity application themes. The scale of TamperedChef-style malware is immense. We found evidence of the two tracked clusters (CL-CRI-1089 and CL-UNK-1090) across more than 50% of Managed Threat Hunting customers. If this number is an accurate representation of the wider community, it shows an operation on a scale rarely observed. The distribution and scale of these campaigns come with high monetary and labor costs. TamperedChef-style actors are likely to have bought much of their success. They have positioned themselves less as malware experts than as advertising and logistics specialists. Code signing as a practice provides authenticity and integrity validation to binaries, but it can be misused by malicious actors. Purchasing code-signing certificates offers a marginal increase in binary trustworthiness. However, they come with strict identity validation and cost, which can deter many malware developers. These requirements did not impede any of the TamperedChef actors, and one of their key strengths comes from a deep understanding of the business side of advertising. The development of several shell companies appeared minimally impactful and provided a reusable pool of code-signing certificates. In the case of CL-UNK-1090, it appeared that renaming existing companies was enough to be granted new, valid certificates, further lowering the barrier for entry. In recent months, we’ve identified a trend of these clusters moving away from code signing. This shift could be occurring because these binaries are becoming better understood and researched. The damage done by identifying an entire campaign through tracking code signers may now outweigh the benefits gained through signing binaries. The rate and scale at which the TamperedChef-style actors deploy new campaigns is incredibly fast. Attackers run tens of campaigns simultaneously, with new ones being developed constantly. The CL-CRI-1089 cluster, in particular, demonstrates a high degree of variation. Each campaign features an entirely new set of TTPs, delivery methods, languages, functionality and C2 structures. This suggests a new codebase for each campaign, and potentially even different developers. The code quality also shows a lack of mature development practices and teams likely inexperienced with malware development. This does somewhat work in favor of TamperedChef binaries, as upon first glance, the C2 methods are not always obvious. In the case of CL-CRI-1089, the codebases are highly variant. However, they share common certificates, demonstrating limited code reuse between campaigns. This may indicate they were created by several development teams or that generative AI was at least partially responsible for the set of campaigns. Distribution infrastructure setup appears to be largely driven using generative AI. This is particularly evident with the distribution websites where the content of pages for different campaigns appears visually similar. However, they have distinct Document Object Model (DOM) structures. This is indicative of a non-deterministic development practice, which is characteristic of content generated by large language models (LLMs). TamperedChef-style samples for all clusters are distributed primarily through malvertisements, sponsored results and search engine marketing techniques. Our telemetry for real-world infection chains commonly shows victims browsing terms like “free calendar prints” or “document formatting” before being served the malvertisements. TamperedChef-style malware establishes a distribution-first approach. Getting installed by the masses is far more important to the operators than managing persistent and reliable C2. While none of the identified TamperedChef malware samples are technically complex, they vary significantly between campaigns. All samples tend to share a common set of TTPs and second-stage payloads, which only serves to further highlight the motivations and risks these TamperedChef-style malware samples pose. These universal TTPs include: Leveraging code signing for the first-stage payloads Implementing a robust persistence mechanism, almost always through scheduled tasks or registry Run keys Initial information gathering and exfiltration typically occurring on install - This usually involves simple data collection, like system version, hostname and active browsers. - However, we have seen more targeted information gathered, including patch levels, user details, domain information, geolocation and screen size. Employing a delayed activation technique to evade detection - Initially, the samples mimic legitimate applications, remaining dormant for days or even weeks. - Upon activation, they trigger the next stage, which typically involves downloading and executing an additional payload delivered via an upstream API. Obfuscating the malicious components - This is the clearest evidence to suggest that these binaries are not just simple adware. - Most of the campaigns we observed used some form of obfuscation or defense evasion techniques for their loader or stealer components. - While obfuscation is used for intellectual property (IP) protection, in this case, the routines were primarily for de-obfuscating incoming payloads within the loader components. - Since no other parts of the binaries were obfuscated, IP protection was likely not the main reason for these methods. TamperedChef-style malware, when activated, can deliver arbitrary payloads, but in practice sticks to two primary categories: adware and browser hijackers or RATs and stealer malware. Which payload it delivers depends on the campaign specifics. TamperedChef rarely deploys both simultaneously. The primary objective of the majority of the TamperedChef-style binaries is to distribute ads or gain some form of control over the user’s browser. This has been achieved via either: Installing a new adversary-controlled default search engine in the user’s primary browser Installing an entirely new adversary-controlled browser (e.g., OneBrowser) Both these methods enable adversaries to control the content searched, ads displayed to victims and, in the case of the browser installation, full control over user cookies and credentials. While adware can be disruptive and undesirable, it does not generally pose a major organizational risk. TamperedChef-style binaries, on the other hand, display a level of stealth, defense evasion and persistence that is unusual and excessive for adware. This likely further indicates that the true threat of the TamperedChef-style malware goes beyond adware and into more insidious use cases. This is backed by real-world cases where attackers have consistently deployed active C2 and stealer-style malware as second stages targeting victims’ browser credentials or for information gathering. These second-stage stealers range in capability, targets and formats but are almost always deployed after a dormancy period of weeks. Evidence of more exotic payloads has been observed too, but far less frequently and not en masse. An example of this was the AppSuite campaign that saw the sporadic installation of proxy-style malware. Distilling the Motivations Our analysis shows that CL-CRI-1089 activity focuses on criminal-style activity targeting credentials, deploying adware and in some cases proxy-style payloads. Based on sample and corporate analysis, the operators of CL-CRI-1089 are globally distributed but centrally operated. In contrast, the motivations behind CL-UNK-1090 activity are far less clear. This activity appears to be solely managed by a much smaller group of entities related, at least in part, to a seemingly successful advertising agency. These samples are all designed to look like adware. However, the samples do not operate like adware, housing RATs with .NET loader-style capabilities that legitimate adware or productivity software do not require. In real world cases, we have not observed the same volume of malicious second stage deployments from samples tracked as CL-UNK-1090 as we have with the CL-CRI-1089 samples. However, second stages deployed by CL-UNK-1090 are more stealthy, existing primarily in memory and include RAT deployments, browser hijackers and adware. Some key preventive steps to combat this threat are: Education: Ensure users are aware of this style of threat and know that even legitimate looking software can carry risks Endpoint/extended detection and response (EDR/XDR): Ensure updated EDRs/XDRs are in place on all hosts within an environment Enterprise browsers: Enterprise browsers can help protect against this threat and ensure that in the event of compromise, saved credentials remain secure Device hardening: Consider hardening user endpoints to prevent the installation of software from untrusted sources Due to the prevalence of these threats, continuous active monitoring and hunting can have a very high return on investments however due to the varied nature of these threats hunting queries vary in effectiveness. If these threats are identified, our general remediation advice is to: Remove and/or quarantine all files associated with the malicious software - These are generally located in the installation folder Ensure that persistence mechanisms such as the created scheduled tasks are removed to prevent reinfection - Consider running a full malware scan of the host as it may identify any second-stage components Consider revoking active tokens for the impacted users and resetting their credentials - It is likely that any browser-based credentials are potentially compromised Review access logs to ensure that the impacted users' credentials are not actively being misused TamperedChef-style campaigns are likely to continue to misuse advertising pipelines to deliver malware, developing and adapting new lures and evasion methods. The prevalence of the CL-CRI-1089, CL-UNK-1090 and CL-UNK-1100 clusters will likely serve as a blueprint for future malvertising campaigns. New trends, such as moving away from using code signing, will require new tracking methods to be developed to remain ahead of these actors' operations. Palo Alto Networks customers are better protected from the threats discussed above through the following products: Cortex XDR and XSIAM help to prevent the threats described in this blog, by employing the Malware Prevention Engine. This approach combines several layers of protection, including Advanced WildFire, Behavioral Threat Protection and the Local Analysis module, designed to prevent both known and unknown malware from causing harm to endpoints. Prisma Browser helps to prevent access to known malicious campaigns using Advanced URL Filtering, Advanced Web Protection (Live Page Scanning) which runs AI models within the browser to detect and block attack patterns, file download scanning and protection on the default search engine. If you think you may have been compromised or have an urgent matter, get in touch with the Unit 42 Incident Response team or call: North America: Toll Free: +1 (866) 486-4842 (866.4.UNIT42) UK: +44.20.3743.3660 Europe and Middle East: +31.20.299.3130 Asia: +65.6983.8730 Japan: +81.50.1790.0200 Australia: +61.2.4062.7950 India: 000 800 050 45107 Palo Alto Networks has shared these findings with our fellow Cyber Threat Alliance (CTA) members. CTA members use this intelligence to rapidly deploy protections to their customers and to systematically disrupt malicious cyber actors. Learn more about the Cyber Threat Alliance. Table 1 lists the signers’ organization noted in code-signing certificates used in the TamperedChef-Style malware samples we found in our research. Table 1. Signers of code-signing certificates from the TamperedChef-style malware samples. Cooking up trouble: How TamperedChef uses signed apps to deliver stealthy payloads – Acronis When the Dash Hits the Fan: Artificial Intelligence Exposes the Homoglyph Hustle – GuidePoint Security EvilAI Operators Use AI-Generated Code and Fake Apps for Far-Reaching Attacks – TrendMicro Malicious Appsuite PDF Editor Spreads Tamperedchef Malware – Truesec The history of AppSuite: the certs of the BaoLoader developer – Expel
unit42.paloaltonetworks.comMay 20, 2026extracted
[Guest Diary] New Malware Libraries means New Signatures, (Fri, May 15th)
Introduction The SHA-256 a8460f446be540410004b1a8db4083773fa46f7fe76fa84219c93daa1669f8f2 is one of the most-observed Outlaw / Shellbot artifacts on the public internet. VirusTotal first ingested it on 5 July 2018 [2]. It is the SHA-256 of the authorized_keys file written by the campaign whose persistence comment string is mdrfckr, a campaign documented in handler diaries, vendor reports, and independent honeypot research for nearly seven years. This diary does not announce a new campaign. The file hash, the public key, the mdrfckr comment string, the chattr -ia .ssh defensive disarm, the chpasswd account hijack, and the /tmp/secure.sh competitor cleanup are all well-described in prior reporting [3][4][5][6][7]. What this diary does add is one new data point in an existing lineage: between 14 and 21 April 2026, my DShield sensor [8] observed the mdrfckr campaign using a third libssh client version that has not, to my knowledge, been published as part of this campaign’s hassh chronology. The botnet’s authorized_keys file is unchanged across four years. Its SSH client library is on its third documented major version. Detection rules pinned to the older hasshes will miss the current generation. The point of this diary is to put the prior reports side by side with my April 2026 observation, document the new hassh, and offer detection-engineering guidance for handlers maintaining mdrfckr-aware rules. What is already known I want to be careful to credit the prior work this diary builds on, because the new contribution is small relative to it. The mdrfckr persistence key was first associated with the Outlaw / Dota family by Trend Micro in 2018 [3], with subsequent updates in 2019 and follow-up reporting from Anomali, Yoroi [9], Juniper [10], CounterCraft [11], Cybereason, and Kaspersky. The recon command sequence and the competitor-cleanup playbook are described across that body of work. None of the file or behaviour signatures discussed in this diary are novel. In late 2022 and early 2023, the port22.dk blog [4][7] published a two-part deep dive on the campaign. Part one (data from October–November 2022) observed 12,913 unique IPs writing the mdrfckr key from a network of 10 honeypots. Crucially, the post introduced hassh-based clustering as a defender’s tool: 99.1% of the observed mdrfckr-key writes shared the hassh 51cba57125523ce4b9db67714a90bf6e, which corresponds to the SSH client banner SSH-2.0-libssh-0.6.0 / SSH-2.0-libssh-0.6.3. Part two (data from December 2022 onward) documented the campaign migrating to a second hassh f555226df1963d1d3c09daf865abdc9a, corresponding to SSH-2.0-libssh_0.9.5 / SSH-2.0-libssh_0.9.6, with ~30,000 unique IPs across the new fingerprint and a 94.5% confidence link. Part two also documented two new related command variants: chattr -ia .ssh; lockr -ia .ssh as a separate command, and lockr -ia .ssh run on its own, executed alongside the original key-write command. In May 2023, a SANS ISC diary by Jesse La Grew [5] presented two example sessions writing the same SHA-256, captured via a cowrie-log enrichment script. One session originated from a DigitalOcean datacentre IP; the other from a VPN-fronted Tencent IP. Both sessions executed the post-December-2022 split-command variant. In May / June 2023, Guy Bruneau’s monthly DShield diary [6] noted the same key-write playbook in honeypot data and attributed it explicitly to the Outlaw group via the original Trend Micro reporting. That is the public chronology this observation extends. What the April 2026 sensor saw Between 2026-04-14 01:23:41 UTC and 2026-04-21 02:22:56 UTC, my DShield sensor logged 24 unique source IPs writing the SHA-256 a8460f446be540410004b1a8db4083773fa46f7fe76fa84219c93daa1669f8f2 to /root/.ssh/authorized_keys (and to other compromised account paths). The cluster wrote 229 authorized_keys modifications across 1,230 SSH sessions and executed 4,133 post-authentication commands. The peak burst occurred on 19 April 2026: 20 of the 24 IPs first connected to the sensor between 06:05:19 UTC and 06:07:30 UTC, a 131-second window. The remaining four IPs appeared on neighbouring days but executed the same playbook with the same key. The defensive-disarm and key-write command observed across every successful session is the post-December-2022 split variant documented by port22 part two: The new data point is the SSH client. The new hassh: libssh 0.11.x Every one of the 24 IPs in the April 2026 cluster advertised the SSH client banner SSH-2.0-libssh_0.11.1 and produced the hassh fingerprint 03a80b21afa810682a776a7d42e5e6fb. This hassh does not match the hashes documented in port22 parts one and two, nor in the May 2023 ISC diary. A hassh is a hash of the SSH client’s advertised cipher, MAC, key-exchange, and compression algorithm lists [12]. Different libssh major versions ship with different default algorithm preferences, so each new libssh version a campaign adopts produces a new hassh. The 2026 hassh 03a80b21afa810682a776a7d42e5e6fb is the third documented entry in this campaign’s libssh version walk, separated from port22’s last published value by approximately three years and one major libssh version (0.9 → 0.10 → 0.11). I do not have a baseline of how prevalent this hassh is across the full DShield sensor population - that is the question I would most like other handlers and DShield operators to help answer. On my single sensor, this hassh accounted for 3,473 SSH log lines across the eight-day window, making it the most active SSH attacker-tooling fingerprint observed during the period. The 24-IP burst: small confirmation of an existing observation Twenty of the 24 cluster IPs first connected within a 131-second window. This is consistent with the coordination behaviour documented at much larger scale by port22, and does not represent a new claim. I mention it only for completeness, and because it has one practical implication for detection: per-source-IP rate limits (fail2ban, sshguard) will not trigger on this pattern because each IP performs only ~10 login attempts. Detection rules useful against this campaign should aggregate by target account rather than by source IP - ten distinct IPs attempting steam:Steam29! against the same host within five minutes is a stronger signature than any individual IP’s behaviour. The cluster IPs and the credential dictionary are listed in the indicators section. None of the credential pairs are new: steam:Steam29!, postgres:q1, dev:dev5, sammy:sammy26, root:AAAaaa111, root:root000@, sysadmin:test123, test1:passwd, tester:testerpass, sammy:12345. This is the existing Outlaw target list. Why this matters for defenders The detection-engineering implication of the libssh version walk is straightforward: hassh-based detection rules written in 2022 or 2023 against 51cba57125523ce4b9db67714a90bf6e or f555226df1963d1d3c09daf865abdc9a will silently miss the 2026 generation of the same campaign. The SHA-256 of the authorized_keys file remains the most reliable single indicator (it has not changed in four years), but operators relying on hassh enrichment as a leading indicator - for example, alerting on hassh values before a successful authentication occurs - should add 03a80b21afa810682a776a7d42e5e6fb to their watch lists. More broadly, the four-year libssh version walk suggests the campaign operator (or operators - the persistence model has always been consistent with shared infrastructure rather than self-propagation in the strict sense) keeps the targeting infrastructure stable while letting the underlying client library age forward. A defender writing a detection rule against this campaign should expect the hassh to change again on a roughly multi-year cadence as libssh ships new defaults, and should pin alerting to the SHA-256, the public key blob, the mdrfckr comment string, and the recon command sequence - none of which have changed since 2018 - rather than to any single hassh value. What I am not claiming The 24-IP April 2026 cluster is much smaller than the populations port22 worked with. I cannot meaningfully extend port22’s hassh-confidence statistics from one sensor’s eight-day window. The 99.1% / 94.5% figures published in 2022 and 2023 should not be extrapolated to the 2026 hassh from this data alone - that calculation requires a multi-sensor population study, which is exactly the kind of analysis ISC handlers and the DShield operator community are positioned to do better than any of my sensors. Indicators authorized_keys SHA-256 (unchanged since 2018):a8460f446be540410004b1a8db4083773fa46f7fe76fa84219c93daa1669f8f2 Public key comment string: mdrfckr April 2026 hassh: 03a80b21afa810682a776a7d42e5e6fb April 2026 SSH client banner: SSH-2.0-libssh_0.11.1 Burst window: 19 April 2026, 06:05:19 → 06:07:30 UTC Credential dictionary: steam:Steam29! ,postgres:q1 ,dev:dev5 ,sammy:sammy26 ,root:AAAaaa111 ,root:root000@ ,sysadmin:test123 ,test1:passwd ,tester:testerpass ,sammy:12345 24 source IPs from the April 2026 cluster (Appendix A) Conclusion The mdrfckr campaign is older than many of the SSH honeypots currently watching it. Its authorized_keys file is approaching its eighth anniversary on VirusTotal and has not been rotated. Its target dictionary, recon sequence, and competitor-cleanup playbook have all remained stable across the four years that public researchers have been tracking the libssh version walk. What changes is the client. The April 2026 hassh 03a80b21afa810682a776a7d42e5e6fb joins 51cba57125523ce4b9db67714a90bf6e and f555226df1963d1d3c09daf865abdc9a as the third documented entry in this campaign’s lineage. Detection rules pinned to either earlier hassh will miss it. I would be very interested to hear from any other DShield operator or ISC handler who has independently observed the 0.11.x hassh writing the SHA-256 above - particularly with population data that would let the community update the hassh-to-mdrfckr confidence figures published by port22 in 2022 and 2023. Acknowledgments Drafting assistance from Claude (Anthropic) [13]. All log review, the hassh and SHA-256 verification, the credential and IP enumeration, and the comparison against prior reporting were done from the sensor’s own logs and the cited public sources. References [3] Trend Micro, https://www.trendmicro.com/en/research/20/b/outlaw-updates-kit-to-kill-older-miner-versions-targets-more-systems.html [4] port22.dk, “mdrfckrs – part one,” March 2023. https://blog.port22.dk/mdrfckrs-part-one/ [5] Jesse La Grew, “More Data Enrichment for Cowrie Logs,” SANS Internet Storm Center, 24 May 2023. https://isc.sans.edu/diary/29878 [6] Guy Bruneau, “DShield Honeypot Activity for May 2023,” SANS Internet Storm Center, 11 June 2023. https://isc.sans.edu/diary/29932 [7] port22.dk, “mdrfckrs – part two,” July 2023. https://blog.port22.dk/mdrfckrs-part-two/ [8] https://isc.sans.edu/honeypot.html [9] Yoroi, “Outlaw is Back: A New Crypto-Botnet Targets European Organizations.” https://yoroi.company/research/outlaw-is-back-a-new-crypto-botnet-targets-european-organizations/ [10] Juniper Threat Research, “Dota3: Is your Internet of Things device moonlighting?” https://blogs.juniper.net/en-us/threat-research/dota3-is-your-internet-of-things-device-moonlighting [11] CounterCraft, “Dota3 malware again and again.” https://www.countercraftsec.com/blog/dota3-malware-again-and-again/
isc.sans.eduMay 15, 2026extracted
Organizations Overlook AI Risk as Governance Fails to Keep Up
Stay connected with press releases from Trend teams in your region. TrendAI™ research reveals pressure to deploy AI for business speed is outpacing control, visibility and accountability DALLAS, March 25, 2026 /PRNewswire/ -- TrendAI™, the enterprise AI security leader from Trend Micro Incorporated (TYO: 4704; TSE: 4704), has published new research revealing that organizations worldwide are pushing ahead with AI deployment despite known security and compliance risks. To read the full report visit: https://www.trendmicro.com/explore/trendai-global-ai-study/ The new global study of 3,700 business and IT decision makers found that 67% have felt pressured to approve AI despite security concerns, with one in seven describing those concerns as "extreme" but overridden to keep pace with competitors and internal demand. Rachel Jin, Chief Platform & Business Officer, Head of TrendAI: "Organizations are not lacking awareness of risk, they're lacking the conditions to manage it. When deployment is driven by competitive pressure rather than governance maturity, you create a situation where AI is embedded into critical systems without the controls needed to manage it safely. This research reenforces our focus on helping organizations drive solid business outcomes with AI while still managing business risk." The risk of pressure-driven AI rollout is exacerbated by governance inconsistencies and unclear responsibility for AI risk that are becoming widespread. The same is true for security teams working on a reactive basis to top-down AI rollout decisions, which often leads to workarounds and increased use of unsanctioned or "shadow" AI tools. Recent TrendAI™ threat research reinforces this shift, showing how attackers are already using AI to automate reconnaissance, accelerate phishing campaigns and lower the barrier to entry for cybercrime, increasing both the speed and scale of attacks. AI adoption is outpacing control Organizations are deploying AI faster than they can manage the associated risks, creating a widening gap between ambition and oversight. 57% say AI is advancing more quickly than they can secure it, while more than half (64%) report only moderate confidence in their understanding of the legal frameworks governing AI. Governance maturity remains low. Only around a third (38%) of organizations have comprehensive AI policies in place, with many still drafting them, and 41% cite unclear regulation or compliance standards as a barrier. In practice, AI is being operationalized before the rules governing its use are fully established. Trust in autonomous AI remains uncertain Confidence in more advanced, autonomous systems is still in the maturing phase. Less than half (48%) believe agentic AI will significantly improve cyber defense in the short term, with ongoing concerns around data access, misuse and lack of oversight. The data shows where those concerns are landing. More than four in ten organizations (44%) say AI agents accessing sensitive data is their biggest risk. Over a third (36%) warn malicious prompts could compromise security, while one in three (33%) point to a growing attack surface for cyber criminals. A similar proportion (33%) fear abuse of trusted AI status and risks linked to autonomous code deployment. At the same time, nearly a third (31%) admit they lack observability or auditability over these systems, raising serious questions about how organizations can control or intervene once agents are deployed. Around 40% of organizations support the introduction of AI "kill switch" mechanisms to shut down systems in the event of failure or misuse, while nearly half remain unsure. This lack of consensus highlights a deeper issue. Organizations are moving towards autonomous AI without agreement on how to retain control when it matters most. "Agentic AI is moving organizations into a new risk category," added Rachel Jin. "Our research shows the concerns are already clear, from sensitive data exposure to loss of oversight. Without visibility and control, organizations are deploying systems they don't fully understand or govern, and that risk is only going to increase unless action is taken." About TrendAI™ TrendAI™, a global leader in AI security, empowers enterprises to innovate fearlessly by securing AI, cloud, networks, endpoints, and data across the modern attack surface. At the core is TrendAI Vision One™, a unified cybersecurity platform that centralizes cyber risk exposure management and security operations to protect the entire AI lifecycle from infrastructure to models to users. The platform is fueled by world-class threat intelligence and insights that protect organizations from hundreds of millions of threats every day. With 6,000 TrendAI™ experts across 75 countries, TrendAI™ empowers security leaders to stay ahead of threats, driving proactive security outcomes across the entire attack surface. This includes critical environments like AWS, Google, Microsoft, and NVIDIA. AI Fearlessly. SOURCE TrendAI
newsroom.trendmicro.comMar 25, 2026extracted
HoneyMyte updates CoolClient and deploys multiple stealers in recent campaigns
Over the past few years, we’ve been observing and monitoring the espionage activities of HoneyMyte (aka Mustang Panda or Bronze President) within Asia and Europe, with the Southeast Asia region being the most affected. The primary targets of most of the group’s campaigns were government entities. As an APT group, HoneyMyte uses a variety of sophisticated tools to achieve its goals. These tools include ToneShell, PlugX, Qreverse and CoolClient backdoors, Tonedisk and SnakeDisk USB worms, among others. In 2025, we observed HoneyMyte updating its toolset by enhancing the CoolClient backdoor with new features, deploying several variants of a browser login data stealer, and using multiple scripts designed for data theft and reconnaissance. Additional information about this threat, including indicators of compromise, is available to customers of the Kaspersky Intelligence Reporting Service. If you are interested, please contact [email protected]. CoolClient backdoor An early version of the CoolClient backdoor was first discovered by Sophos in 2022, and TrendMicro later documented an updated version in 2023. Fast forward to our recent investigations, we found that CoolClient has evolved quite a bit, and the developers have added several new features to the backdoor. This updated version has been observed in multiple campaigns across Myanmar, Mongolia, Malaysia and Russia where it was often deployed as a secondary backdoor in addition to PlugX and LuminousMoth infections. In our observations, CoolClient was typically delivered alongside encrypted loader files containing encrypted configuration data, shellcode, and in-memory next-stage DLL modules. These modules relied on DLL sideloading as their primary execution method, which required a legitimate signed executable to load a malicious DLL. Between 2021 and 2025, the threat actor abused signed binaries from various software products, including BitDefender, VLC Media Player, Ulead PhotoImpact, and several Sangfor solutions. The latest CoolClient version analyzed in this article abuses legitimate software developed by Sangfor. Below, you can find an overview of how it operates. It is worth noting that its behavior remains consistent across all variants, except for differences in the final-stage features. However, it is worth noting that in another recent campaign involving this malware in Pakistan and Myanmar, we observed that HoneyMyte has introduced a newer variant of CoolClient that drops and executes a previously unseen rootkit. A separate report will be published in the future that covers the technical analysis and findings related to this CoolClient variant and the associated rootkit. CoolClient functionalities In terms of functionality, CoolClient collects detailed system and user information. This includes the computer name, operating system version, total physical memory (RAM), network details (MAC and IP addresses), logged-in user information, and descriptions and versions of loaded driver modules. Furthermore, both old and new variants of CoolClient support file upload to the C2, file deletion, keylogging, TCP tunneling, reverse proxy listening, and plugin staging/execution for running additional in-memory modules. These features are still present in the latest versions, alongside newly added functionalities. In this latest variant, CoolClient relies on several important files to function properly: Parameter modes in second-stage DLL CoolClient typically requires three parameters to function properly. These parameters determine which actions the malware is supposed to perform. The following parameters are supported. Final stage DLL The write.exe process decrypts and launches the main.dat file, which contains the third (final) stage DLL. CoolClient’s core features are implemented in this DLL. When launched, it first checks whether the keylogger, clipboard stealer, and HTTP proxy credential sniffer are enabled. If they are, CoolClient creates a new thread for each specific functionality. It is worth noting that the clipboard stealer and HTTP proxy credential sniffer are new features that weren’t present in older versions. Clipboard and active windows monitor A new feature introduced in CoolClient is clipboard monitoring, which leverages functions that are typically abused by clipboard stealers, such as GetClipboardData and GetWindowTextW, to capture clipboard information. CoolClient also retrieves the window title, process ID and current timestamp of the user’s active window using the GetWindowTextW API. This information enables the attackers to monitor user behavior, identify which applications are in use, and determine the context of data copied at a given moment. The clipboard contents and active window information are encrypted using a simple XOR operation with the byte key 0xAC, and then written to a file located at C:\ProgramData\AppxProvisioning.xml. HTTP proxy credential sniffer Another notable new functionality is CoolClient’s ability to extract HTTP proxy credentials from the host’s HTTP traffic packets. To do so, the malware creates dedicated threads to intercept and parse raw network traffic on each local IP address. Once it is able to intercept and parse the traffic, CoolClient starts extracting proxy authentication credentials from HTTP traffic intercepted by the malware’s packet sniffer. The function operates by analyzing the raw TCP payload to locate the Proxy-Connection header and ensure the packet is relevant. It then looks for the Proxy-Authorization: Basic header, extracts and decodes the Base64-encoded credential and saves it in memory to be sent later to the C2. C2 command handler The latest CoolClient variant uses TCP as the main C2 communication protocol by default, but it also has the option to use UDP, similar to the previous variant. Each incoming payload begins with a four-byte magic value to identify the command family. However, if the command is related to downloading and running a plugin, this value is absent. If the client receives a packet without a recognized magic value, it switches to plugin mode (mechanism used to receive and execute plugin modules in memory) for command processing. 0xFFAABBCC – Beacon and configuration commands Below is the command menu to manage client status and beaconing: 0xFFAABBCD – Operational commands This command group implements functionalities such as data theft, proxy setup, and file manipulation. The following is a breakdown of known subcommands: CoolClient plugins CoolClient supports multiple plugins, each dedicated to a specific functionality. Our recent findings indicate that the HoneyMyte group actively used CoolClient in campaigns targeting Mongolia, where the attackers pushed and executed a plugin named FileMgrS.dll through the C2 channel for file management operations. Further sample hunting in our telemetry revealed two additional plugins: one providing remote shell capability (RemoteShellS.dll), and another focused on service management (ServiceMgrS.dll). ServiceMgrS.dll – Service management plugin This plugin is used to manage services on the victim host. It can enumerate all services, create new services, and even delete existing ones. The following table lists the command IDs and their respective actions. FileMgrS.dll – File management plugin A few basic file operations are already supported in the operational commands of the main CoolClient implant, such as listing directory contents and deleting files. However, the dedicated file management plugin provides a full set of file management capabilities. RemoteShellS.dll – Remote shell plugin Based on our analysis of the main implant, the C2 command handler did not implement remote shell functionality. Instead, CoolClient relied on a dedicated plugin to enable this capability. This plugin spawns a hidden cmd.exe process, redirecting standard input and output through pipes, which allows the attacker to send commands into the process and capture the resulting output. This output is then forwarded back to the C2 server for remote interaction. Browser login data stealer While investigating suspicious ToneShell backdoor traffic originating from a host in Thailand, we discovered that the HoneyMyte threat actor had downloaded and executed a malware sample intended to extract saved login credentials from the Chrome browser as part of their post-exploitation activities. We will refer to this sample as Variant A. On the same day, the actor executed a separate malware sample (Variant B) targeting credentials stored in the Microsoft Edge browser. Both samples can be considered part of the same malware family. During a separate threat hunting operation focused on HoneyMyte’s QReverse backdoor, we retrieved another variant of a Chrome credential parser (Variant C) that exhibited significant code similarities to the sample used in the aforementioned ToneShell campaign. The malware was observed in countries such as Myanmar, Malaysia, and Thailand, with a particular focus on the government sector. The following table shows the variants of this browser credential stealer employed by HoneyMyte. These stealers may be part of a new malware toolset used by HoneyMyte during post-exploitation activities. Initial infection As part of post-exploitation activity involving the ToneShell backdoor, the threat actor initially executed the Variant A stealer, which targeted Chrome credentials. However, we were unable to determine the exact delivery mechanism used to deploy it. A few minutes later, the threat actor executed a command to download and run the Variant B stealer from a remote server. This variant specifically targeted Microsoft Edge credentials. Within the same hour that Variant B was downloaded and executed, we observed the threat actor issue another command to exfiltrate the Firefox browser cookie file (cookies.sqlite) to Google Drive using a curl command. Variant C analysis Unlike Variants A and B, which use hardcoded file paths, the Variant C stealer accepts two runtime arguments: file paths to the browser’s Login Data and Local State files. This provides greater flexibility and enables the stealer to target any Chromium-based browser such as Chrome, Edge, Brave, or Opera, regardless of the user profile or installation path. An example command used to execute Variant C is as follows: In this context, the Login Data file is an SQLite database that stores saved website login credentials, including usernames and AES-encrypted passwords. The Local State file is a JSON-formatted configuration file containing browser metadata, with the most important value being encrypted_key, a Base64-encoded AES key. It is required to decrypt the passwords stored in the Login Data database and is also encrypted. When executed, the malware copies the Login Data file to the user’s temporary directory as chromeTmp. To retrieve saved credentials, the malware executes the following SQL query on the copied database: This query returns the login URL, stored username, and encrypted password for each saved entry. Next, the malware reads the Local State file to extract the browser’s encrypted master key. This key is protected using the Windows Data Protection API (DPAPI), ensuring that the encrypted data can only be decrypted by the same Windows user account that created it. The malware then uses the CryptUnprotectData API to decrypt this key, enabling it to access and decrypt password entries from the Login Data SQLite database. With the decrypted AES key in memory, the malware proceeds to decrypt each saved password and reconstructs complete login records. Finally, it saves the results to the text file C:\Users\Public\Libraries\License.txt. Login data stealer’s attribution Our investigation indicated that the malware was consistently used in the ToneShell backdoor campaign, which was attributed to the HoneyMyte APT group. Another factor supporting our attribution is that the browser credential stealer appeared to be linked to the LuminousMoth APT group, which has previously been connected to HoneyMyte. Our analysis of LuminousMoth’s cookie stealer revealed several code-level similarities with HoneyMyte’s credential stealer. For example, both malware families used the same method to copy targeted files, such as Login Data and Cookies, into a temporary folder named ChromeTmp, indicating possible tool reuse or a shared codebase. Both stealers followed the same steps: they checked if the original Login Data file existed, located the temporary folder, and copied the browser data into a file with the same name. Based on these findings, we assess with high confidence that HoneyMyte is behind this browser credential stealer, which also has a strong connection to the LuminousMoth APT group. Document theft and system information reconnaissance scripts In several espionage campaigns, HoneyMyte used a number of scripts to gather system information, conduct document theft activities and steal browser login data. One of these scripts is a batch file named 1.bat. 1.bat – System enumeration and data exfiltration batch script The script starts by downloading curl.exe and rar.exe into the public folder. These are the tools used for file transfer and compression. It then collects network details and downloads and runs the nbtscan tool for internal network scanning. During enumeration, the script also collects information such as stored credentials, the result of the systeminfo command, registry keys, the startup folder list, the list of files and folders, and antivirus information into a file named log.dat. It then uploads this file via FTP to http://113.23.212[.]15/pub/. Next, it deletes both log.dat and the nbtscan executable to remove traces. The script then terminates browser processes, compresses browser-related folders, retrieves FileZilla configuration files, archives documents from all drives with rar.exe, and uploads the collected data to the same server. Finally, it deletes any remaining artifacts to cover its tracks. Ttraazcs32.ps1 – PowerShell-based collection and exfiltration The second script observed in HoneyMyte operations is a PowerShell file named Ttraazcs32.ps1. Similar to the batch file, this script downloads curl.exe and rar.exe into the public folder to handle file transfers and compression. It collects computer and user information, as well as network details such as the public IP address and Wi-Fi network data. All gathered information is written to a file, compressed into a password-protected RAR archive and uploaded via FTP. In addition to system profiling, the script searches multiple drives including C:\Users\Desktop, Downloads, and drives D: to Z: for recently modified documents. Targeted file types include .doc, .xls, .pdf, .tif, and .txt, specifically those changed within the last 60 days. These files are also compressed into a password-protected RAR archive and exfiltrated to the same FTP server. t.ps1 – Saved login data collection and exfiltration The third script attributed to HoneyMyte is a PowerShell file named t.ps1. The script requires a number as a parameter and creates a working directory under D:\temp with that number as the directory name. The number is not related to any identifier. It is simply a numeric label that is probably used to organize stolen data by victim. If the D drive doesn’t exist on the victim’s machine, the new folder will be created in the current working directory. The script then searches the system for Chrome and Chromium-based browser files such as Login Data and Local State. It copies these files into the target directory and extracts the encrypted_key value from the Local State file. It then uses Windows DPAPI (System.Security.Cryptography.ProtectedData) to decrypt this key and writes the decrypted Base64-encoded key into a new file named Local State-journal in the same directory. For example, if the original file is C:\Users\$username \AppData\Local\Google\Chrome\User Data\Local State, the script creates a new file C:\Users\$username\AppData\Local\Google\Chrome\User Data\Local State-journal, which the attacker can later use to access stored credentials. Once the credential data is ready, the script verifies that both rar.exe and curl.exe are available. If they are not present, it downloads them directly from Google Drive. The script then compresses the collected data into a password-protected archive (the password is “PIXELDRAIN”) and uploads it to pixeldrain.com using the service’s API, authenticated with a hardcoded token. Pixeldrain is a public file-sharing service that attackers abuse for data exfiltration. This approach highlights HoneyMyte’s shift toward using public file-sharing services to covertly exfiltrate sensitive data, especially browser login credentials. Conclusion Recent findings indicate that HoneyMyte continues to operate actively in the wild, deploying an updated toolset that includes the CoolClient backdoor, a browser login data stealer, and various document theft scripts. With capabilities such as keylogging, clipboard monitoring, proxy credential theft, document exfiltration, browser credential harvesting, and large-scale file theft, HoneyMyte’s campaigns appear to go far beyond traditional espionage goals like document theft and persistence. These tools indicate a shift toward the active surveillance of user activity that includes capturing keystrokes, collecting clipboard data, and harvesting proxy credential. Organizations should remain highly vigilant against the deployment of HoneyMyte’s toolset, including the CoolClient backdoor, as well as related malware families such as PlugX, ToneShell, Qreverse, and LuminousMoth. These operations are part of a sophisticated threat actor strategy designed to maintain persistent access to compromised systems while conducting high-value surveillance activities. Indicators of compromise CoolClient F518D8E5FE70D9090F6280C68A95998F libngs.dll 1A61564841BBBB8E7774CBBEB3C68D5D loader.dat AEB25C9A286EE4C25CA55B72A42EFA2C main.dat 6B7300A8B3F4AAC40EEECFD7BC47EE7C time.dat CoolClient plugins 7AA53BA3E3F8B0453FFCFBA06347AB34 ServiceMgrS.dll A1CD59F769E9E5F6A040429847CA6EAE FileMgrS.dll 1BC5329969E6BF8EF2E9E49AAB003F0B RemoteShellS.dll Browser login data stealer 1A5A9C013CE1B65ABC75D809A25D36A7 Variant A E1B7EF0F3AC0A0A64F86E220F362B149 Variant B DA6F89F15094FD3F74BA186954BE6B05 Variant C Scripts C19BD9E6F649DF1DF385DEEF94E0E8C4 1.bat 838B591722512368F81298C313E37412 Ttraazcs32.ps1 A4D7147F0B1CA737BFC133349841AABA t.ps1 CoolClient C2 account.hamsterxnxx[.]com popnike-share[.]com japan.Lenovoappstore[.]com FTP server 113.23.212[.]15
securelist.comJan 27, 2026extracted
Battling Cryptojacking, Botnets, and IABs [Guest Diary], (Thu, Jan 15th)
[This is a Guest Diary by Matthew Presnal, an ISC intern as part of the SANS.edu BACS program] Cryptojacking and botnets can pose a greater threat than a simple drain of resources. These organizations have been known to engage in “DDoS for Hire” or even selling off footholds, acting as Initial Access Brokers (IABs). To better understand how to get ahead of the adversary, I am going to walk you through the real-world attacks observed on my DShield honeypot and attempt to better predict their next steps. Early Recognition As we know from a certain company's model for stopping attacks (I'll let you fill in the blanks), the earlier you are able to break the chain, the better the outcome. While the ideal situation is to have impenetrable defenses, thus making it so you have nothing to worry about, that is just not realistic. If we are able to recognize early signs of a potential attack, i.e recon, we can posture or even preempt the attack by implementing hardening that we may otherwise avoid due to operational impact. The screenshot below is from recent activity observed on my honeypot. In this instance, the IP points back to a Digital Ocean machine, but I have numerous other accounts of this exact script being run to enumerate the system from several other IPs outside of this range. In the interest of readability, I have supplied the enumeration script here: At this stage, the threat actor already has access (this resulted from SSH spraying), and they are enumerating the machine for kernel info, system architecture, uptime, CPU model and capabilities, GPU info, binary versions, and login info. They then output all of this information in a standardized format to be parsed, either via an automated process or handed off to someone to start building persistence/determining if the system is suitable for the botnet. In a real environment recognizing this as a potential adversarial first step does a few different things for us in addition to activating the Incident Response Plan (IRP): 1. It gives us the opportunity to ensure adequate coverage of the network 2. An opportunity to start diverting traffic away from a known compromised machine and introducing isolation/quarantining the machine 3. The ability to “play by play” adversarial actions and build detection rules that can be implemented across the network 4. Roll out hardening tailored to the adversarial activity to enact the “Pyramid of Pain” at the TTP level (Bonus points if you are able to attribute the attack real-time) Actions on Objective The attack chain below was witnessed on the same honeypot, and I believe it to be part of the same “run book” presumably carried out by the cryptojacking and botnet organization “Outlaw": Actor IP: 197.221.232.44 Kibana GeoIP: Harare, Zimbabwe The first several lines of this chain are more enumeration and situational awareness, gathering more system info, user info, processes, and even which users are logged in with the ‘w’ command. The first real exploitation action starts with the recursive remove command, prepping the system for the SSH persistence mechanism Outlaw is known for. Malware In the interest of brevity, this section will not go into any real depth but will rather attempt to further flesh out the post-exploitation phase of the attack. As you can see in the screenshots below, the hash of the malware downloaded on the honeypot is identified as a Trojan and a Miner, and it has references to a ‘zombie’ within the strings of the code itself suggesting likely botnet involvement. This malware stems from a series of Chinese IPs that are all within the same ASN. While I cannot directly relate these to the suspected “Outlaw” scripts earlier, the Kibana logs are interesting for these IPs. They all start with a successful SSH connection and quickly move to an SFTP transfer of the malware. The malware itself appears to be a Go binary which is a deviation from the expected “Perl-based backdoor” noted by TrendMicro [4]. With this unlikely to be “Outlaw” directly, I am choosing to include this activity for two main reasons: 1) I am using “Outlaw” activity as more of a threat model rather than the group being the primary subject for this post 2) Each occurrence of this payload is precluded by activity identical or nearly identical to the scanning and persistence discussed earlier This behavior is suggestive of either an evolution of processes by implementing specialization within the organization or the IAB-like activity mentioned earlier. This malware was the result of: shield@dshield:/srv/cowrie/var/lib/cowrie/downloads$ sudo strings -a 649eecfd7b02b59248ef5d1fce494e2f1b9d2fc20eef43fc4c74be8bc10ce1c1 -n 80 | less What Can Be Done? In the Early Recognition section, I gave a few suggestions of what you can do to cutoff the threat actor at the first sign of intrusion. This section aims to use some best practices to defend the network against this type of activity. Enforce strong authentication controls for remote access by disabling password-based SSH authentication in favor of key-based authentication Enforce multi-factor authentication (MFA) for administrative access were supported Use TCP Wrappers (/etc/hosts.allow and /etc/hosts.deny) as a defense-in-depth mechanism to restrict access to known management networks and reduce unauthenticated connection attempts Apply file integrity monitoring (FIM) to critical system and configuration files, including /etc/hosts.allow, /etc/hosts.deny, user .ssh directories, authorized_keys, and cron configurations Monitor for post-exploitation enumeration activity by alerting on rapid execution of common reconnaissance commands such as uname, lscpu, cat /proc/cpuinfo, w, top, and crontab -l Detect and investigate destructive or preparatory commands often used to enable persistence, such as recursive deletion of .ssh directories, use of chattr Routinely audit user accounts, group memberships, and privilege assignments Centralize authentication, process execution, and network logs, ensuring a minimum of 90 days log retention to support incident response and threat hunting activities Perform routine patching and vulnerability management for operating systems and exposed services to reduce the effectiveness of automated exploitation and scanning frameworks Test and exercise the incident response plan (IRP) to ensure rapid containment, isolation, and investigation can occur when early indicators of compromise are detected Consider investing resources into Threat Hunting and Cyber Threat Intelligence to better identify and predict adversarial activity Conclusion This style of attack (Password spray of SSH -> System enumeration -> Persistence mechanisms via SSH -> Transfer of malicious file) is the most common attack I witnessed while monitoring DShield via Kibana. While it makes sense for a cybercrime organization to carry this out due to the amount of automation that can be used, the actual attack chains seem to be relatively simple to defend. We have seen cybercrime organizations specialize and organize in a more corporate structure, meaning certain organizations deal in initial access, others exploitation, and other actions on objective. It seems cryptojacking goups like ‘Outlaw’ would fall more on the initial access side with them choosing whether or not the victim fits their use case. What we can do is continue to encourage defenders to stay up to date with CTI and take a proactive approach to threat hunting we can make the job of the adversary significantly more difficult. Ultimately stifling the IABs, reducing funding to lower tiered groups, and potentially destabilizing the structure and segmentation of roles within the cybercrime field. [1] https://isc.sans.edu/diary/Decoding+the+Patterns+Analyzing+DShield+Honeypot+Activity+Guest+Diary/30428 [2] https://www.attackiq.com/glossary/pyramid-of-pain-2/ [3] https://isc.sans.edu/diary/DShield+Honeypot+Activity+for+May+2023/29932 [4] https://www.trendmicro.com/en_us/research/19/f/outlaw-hacking-groups-botnet-observed-spreading-miner-perl-based-backdoor.html [5] https://krebsonsecurity.com/tag/ddos-for-hire/ [6] https://attack.mitre.org/ [7] https://www.sans.edu/cyber-security-programs/bachelors-degree/ ----------- Guy Bruneau IPSS Inc. My GitHub Page Twitter: GuyBruneau gbruneau at isc dot sans dot edu
isc.sans.eduJan 15, 2026extracted
Trend Micro Predicts 2026 as the Year Scams Become AI-Driven, AI-Scaled, and Emotion-Engineered
Stay connected with press releases from Trend teams in your region. DALLAS, December 3, 2025 – Trend Micro Incorporated (TYO: 4704; TSE: 4704), a global cybersecurity leader, today released its 2026 Consumer Security Predictions Report, warning that the coming year will see scams reach unprecedented AI-driven scale as automation reshapes how fraudsters target victims. From synthetic relationships to multi-channel fraud journeys, cybercriminals are merging automation with emotional manipulation, creating unprecedented speed, realism, and scale. To read the full report, 2026 Scam Predictions: How AI and Emotion Are Re-Engineering Global Scams, please visit: https://www.trendmicro.com/explore/2026-consumer-threat-predictions Lynette Owens, Vice President of Consumer Education & Marketing at Trend Micro: “We are entering an era where cybercriminals are employing AI to make their deception both effortless and highly personalized. Consumers are being targeted in ways that are harder for them to discern by the once easily recognizable hallmarks of suspicious content. The challenge ahead is how to ensure consumers have both the skills and tools to protect themselves from modern digital threats versus those of the past.” The report highlights how AI-generated personas, deepfake media, and agentic automation are transforming global scam operations. Fraudsters can now clone voices, write personalized messages, and shift conversations across SMS, chat apps, and fake websites more efficiently than ever before. Furthermore, multi-channel scams, where victims are lured from social media or text messages into encrypted chats and fraudulent payment pages, will become the dominant pattern in 2026. Relationship and investment scams will continue to drive the highest financial losses. AI chatbots, deepfake companions, and manipulated imagery will blur the line between real and synthetic interactions, while crypto-related investment fraud will expand through sophisticated scam-as-a-service networks. At the same time, instant payment fraud is expected to surge as criminals exploit peer-to-peer money apps and irreversible transfers. High volume impersonation scams, including delivery, billing, and subscription renewal fraud, will remain the most common global threat. These campaigns increasingly rely on localized smishing kits and professional-grade branding, making them nearly indistinguishable from legitimate communications. To help consumers navigate this new era of AI-driven scams, Trend Micro highlights its ScamCheck tool as a key protection layer. ScamCheck allows users to instantly verify suspicious texts, links, social messages, and phone numbers – directly addressing the multi-channel fraud journeys outlined in the report. It analyzes impersonation patterns, risky URLs, and behavioral cues commonly seen in delivery, billing, investment, and relationship scams. ScamCheck gives consumers immediate verification guidance, helping them spot AI-engineered or highly polished scams that bypass traditional forms of detection. Trend advises consumers worldwide to adopt new “verification-first” habits as tactics evolve. AI-enhanced fraud is making older warning signs, such as poor spelling or grammar, obsolete. Instead, users must rely on identity checks, cross-channel verification, and an awareness that even convincing messages can be engineered to manipulate trust. Trend’s 2026 consumer predictions underscore a future where scams operate as AI-scaled ecosystems. Those who stay informed, use secure-by-design platforms, and adopt modern verification practices will be best equipped to protect themselves in an increasingly deceptive digital world. To learn more about Trend Micro’s 2026 Consumer Threat Predictions, visit https://www.trendmicro.com/explore/2026-consumer-threat-predictions About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information between people, governments, and enterprises. Trend leverages decades of security expertise and the power of AI to protect more than 500,000 enterprises and millions of individuals worldwide. As a leader in consumer cybersecurity and the fight against scams, Trend delivers industry-first and award-winning products to protect millions of consumers from modern online threats. With 7,000 employees across 70 countries, Trend Micro enables organizations to simplify and secure their connected world. Learn more at www.trendmicro.com. Media Contact: Trend Micro Communications 817-522-7911 [email protected]
newsroom.trendmicro.comDec 3, 2025extracted
Trend Micro Predicts 2026 as the Year Cybercrime Becomes Fully Industrialized
Stay connected with press releases from Trend teams in your region. DALLAS, Nov. 25, 2025 /PRNewswire/ -- Trend Micro Incorporated (TYO: 4704; TSE: 4704), a global cybersecurity leader, today released its annual Security Predictions Report for 2026, warning that the coming year will mark the true industrialization of cybercrime. Artificial intelligence (AI) and automation are now enabling threat actors to run entire campaigns autonomously, from reconnaissance to extortion, creating unprecedented speed, scale, and complexity for enterprise defenders. To read the full report, The AI-fication of Cyberthreats - Trend Micro Security Predictions for 2026, please visit: https://www.trendmicro.com/vinfo/us/security/research-and-analysis/predictions/the-ai-fication-of-cyberthreats-trend-micro-security-predictions-for-2026 Ryan Flores, Lead of Forward-Looking Threat Research at Trend: "2026 will be remembered as the year cybercrime stopped being a service industry and became a fully automated one. We are entering an era where AI agents will discover, exploit, and monetize weaknesses without human input. The challenge for defenders is no longer simply detecting attacks, it's keeping pace with the machine-driven tempo of threats." The report highlights how generative AI and agentic systems are transforming the economics of cybercrime. Autonomous intrusion campaigns that adapt in real time, polymorphic malware that constantly rewrites its own code, and deepfake-driven social engineering will be standard tools for attackers. The same automation also threatens to flood businesses with synthetic code, poisoned AI models, and flawed modules hidden inside legitimate workflows, blurring the line between innovation and exploitation. Hybrid cloud environments, software supply chains, and AI infrastructures are expected to be the primary targets in 2026. Poisoned open-source packages, malicious container images, and over-privileged cloud identities will become common attack vectors, while state-sponsored groups will increasingly turn to "harvest-now, decrypt-later" strategies to future-proof espionage against the advance of quantum computing. Ransomware is evolving into an AI-powered ecosystem capable of managing itself, e.g. identifying victims, exploiting weaknesses, and even negotiating with targets via automated "extortion bots." Trend threat researchers expect these campaigns to become faster, harder to trace, and more persistent, driven by data rather than encryption alone. Trend advises organizations worldwide to move from reactive defense to proactive resilience by embedding security across every layer of AI adoption, cloud operations, and supply chain management. Organizations that integrate ethical AI use, adaptive defense, and human oversight will be the ones best positioned to succeed in the future. Trend's 2026 predictions outline a path forward based on visibility, automation with human validation, and a cultural shift that treats security as strategic infrastructure. Those who innovate securely, by balancing speed with governance and intelligence with ethics, will set the standard for trust and resilience in an increasingly autonomous world. About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information between people, governments, and enterprises. Trend leverages security expertise and AI to protect more than 500,000 enterprises and millions of individuals across clouds, networks, endpoints, and devices worldwide. At the core is Trend Vision One™, the only AI-powered enterprise cybersecurity platform that centralizes cyber risk exposure management and security operations, delivering layered protection across on-premises, hybrid, and multi-cloud environments. The unmatched threat intelligence delivered by Trend empowers organizations to proactively defend against hundreds of millions of threats every day. Proactive security starts here. TrendMicro.com SOURCE Trend Micro Incorporated
newsroom.trendmicro.comNov 25, 2025extracted
New Trend Micro Survey Shows Economic Strain and Overconfidence put Holiday Shoppers at Greater Risk of Online Scams
Stay connected with press releases from Trend teams in your region. From job losses to rising costs, consumers are spending less, but risking more as they chase online deals too good to be true DALLAS, November 19, 2025 – Trend Micro Incorporated, a global leader in cybersecurity, today released its Holidays, Scams, and AI study, which surveyed over 6,500 consumers across six countries (United States, United Kingdom, Australia, New Zealand, Singapore, and Taiwan). The 2,100 U.S. participants revealed a worrying disconnect: people believe they can spot a scam, but many admit to already having been targeted by scammers. The findings come as consumers face mounting financial pressures, rising living costs, and a flood of AI-fueled scams that are increasingly difficult to detect. A majority (56%) of Americans indicated that they are either very or extremely confident in their ability to spot a scam. Additionally, nearly half (43%) of Americans said they’ve already seen what they believed to be a scam promoting discounted prices for holiday gifts or travel this season. One-third (33%) of respondents reported that they had already seen an online advertisement, email, text message, social media post, or website related to holiday gifts or travel this year that was fraudulently impersonating a well-known brand. But consumers’ behavior tells a different story: 86% of U.S. respondents would consider buying a gift or booking travel from a seller they’ve never heard of because it was a very good price. Additionally, over half (54%) of respondents plan to spend more time looking for end of year holiday shopping and travel deals – widening the attack range for cybercriminals. Lynette Owens, VP of Consumer Education & Marketing at Trend: “People are under real pressure this year: Consumers are working with tighter wallets, higher anxiety, and a false sense of digital confidence. Scammers know this and are using age-old manipulation tactics together with AI to exploit shoppers faster and more effectively than ever before, raising the urgency for consumers to fight back and protect themselves from scams.” Even as they appear increasingly vulnerable to scams, consumers are not increasingly cautious. Fewer Americans in 2025 (54%) reported being at least “moderately worried” about getting scammed compared to similar Trend research from 2024 (58%). Americans are also potentially at greater risk this year, with nearly a quarter (23%) reporting they had already been victims of an online scam in 2025, compared to 17% reporting the same in the 2024 study. Interestingly, 32% of those who earn at least $150,000 a year report having been scammed this year, the highest income group surveyed. This suggests that while some groups may be looking harder for bargains online, everyone could be a target regardless of income. The study also uncovered some wide differences by age. 70% of U.S. respondents aged 18-44 claim they feel very confident in being able to spot a scam, but the number drastically decreases with age, with only 36% of those aged 65+ saying the same. Moreover, younger groups are more likely to participate in risky online shopping behavior, with 54% of those aged 25-44 willing to purchase from a brand they had never heard of before, while only 24% of those aged 65+ say they would do the same. The increasing prevalence of AI further complicates safe holiday shopping. Over half of U.S. respondents (52%) said they are definitely or are considering using AI technology (a tool, browser, and/or shopping assistant) to help them with holiday shopping this season. Additionally, a staggering 82% of consumers believe they will see AI generated images or videos online during the holiday season. Today’s scammers are using AI to formulate multi-step, multi-channel, and hyper-personalized scams. This new generation of scams doesn’t come as one-off messages. They unfold as stories designed to lure victims step-by-step. To help quell this growing trend, Trend developed Scam Radar, a new feature within its ScamCheck tool, designed to proactively scan for scam signals across texts, calls, websites, and social media links. Instead of reacting after the fact, Scam Radar connects the dots in real time, issuing early alerts before consumers engage with the tactics employed by scammers. Trend also recently released a research paper titled “Reimagining Fraud Operations: The Rise of AI-Powered Scam Assembly Lines” that details how cybercriminals are using AI to make old scams faster, smarter, and more convincing than ever. “While consumers see the upside of AI to help, AI is also being used to cause them harm. Scammers are employing it to develop sophisticated scams that take advantage of consumers who are looking for a bargain while under financial stress,” said Owens. “It is increasingly difficult for even AI-savvy shoppers to detect fake products, websites, or advertisements, raising the urgency to use tools like Scam Check to fight back.” In addition to ScamCheck, Trend suggests several tips to empower consumers to fight scams this holiday season: This year, holiday scams are more convincing, more automated, and more personal than ever. But with the right awareness and tech tools, consumers can protect themselves, their loved ones, and their wallets. The Holidays, AI, and Scams survey was conducted online from October 31 – November 10 among 6,536 consumers in Australia, New Zealand, Singapore, Taiwan, the United Kingdom and the United States. To learn more about holiday scams, visit trendmicro.com. About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information between people, governments, and enterprises. Trend leverages decades of security expertise and the power of AI to protect more than 500,000 enterprises and millions of individuals worldwide. As a leader in consumer cybersecurity and the fight against scams, Trend delivers industry-first and award-winning products to protect millions of consumers from modern online threats. With 7,000 employees across 70 countries, Trend Micro enables organizations to simplify and secure their connected world. Learn more at www.trendmicro.com.
newsroom.trendmicro.comNov 19, 2025extracted
Digital Doppelgangers: Anatomy of Evolving Impersonation Campaigns Distributing Gh0st RAT
We have identified two interconnected malware campaigns active throughout 2025, using large-scale brand impersonation to deliver Gh0st remote access Trojan (RAT) variants to Chinese-speaking users. From the first campaign to the second, the adversary advanced from simple droppers to complex, multi-stage infection chains that misuse legitimate, signed software to bypass modern defenses. This report provides a detailed breakdown of the campaigns' anatomy, offering new intelligence on the attackers' operational playbook. We analyze an initial campaign from February–March 2025 that mimicked three brands across over 2,000 domains and a more sophisticated campaign starting in May 2025 that impersonated over 40 applications. The impersonated software primarily includes widely used enterprise tools, secure messaging apps, gaming platforms and popular AI software. By analyzing the evolution of the attack methods, infrastructure and targeting, we establish a clear operational playbook. Understanding the adversary’s adaptive tactics, techniques and procedures (TTPs), such as using cloud infrastructure for payload delivery and DLL side-loading for evasion, provides crucial insights for enhancing security postures. Our analysis is based on data from Palo Alto Networks products, including Advanced URL Filtering and Advanced WildFire, which provided visibility into the malware's behavior and infection chains. This internal data was supplemented by passive DNS (pDNS) analysis and open-source intelligence. We provide organizations with indicators of compromise (IoCs) to mitigate against this threat. Palo Alto Networks customers are better protected from this activity through the following products and services: Advanced WildFire Advanced URL Filtering and Advanced DNS Security Advanced Threat Prevention Cortex XDR and XSIAM Cortex Cloud DSPM If you think you might have been compromised or have an urgent matter, contact the Unit 42 Incident Response team. In recent years, malware campaigns specifically tailored to target Chinese-speaking users globally have emerged as a notable trend in the threat landscape. These operations demonstrate a complex understanding of the target demographic's digital ecosystem and online behaviors. The lures used are often not generic. Instead, attackers carefully select them to appeal to this specific audience. Attackers frequently impersonate the following types of applications: Software that is widely popular within the community (e.g., Youdao dictionary or Sogou browser) Tools used to circumvent state-imposed internet restrictions (e.g., VPNs and encrypted messaging applications) How would potential victims find these malicious sites impersonating legitimate software? Attackers have a variety of options. They could generate traffic to these sites through malicious online ads or search engine poisoning. Attackers can also post on social media and other online forums to promote these sites. Email is another vector for leading potential victims to these sites. The choice to target people seeking tools to bypass censorship is particularly strategic. This suggests an adversary who is interested in people already attempting to operate outside of easily monitored channels, making them prime targets for surveillance or espionage. The final payload in these campaigns is often a RAT that grants the attacker comprehensive control over a compromised system. The Gh0st RAT and its many variants are a prominent choice, particularly for Chinese-nexus cybercrime and espionage actors who have used these tools for over a decade. We refer to this initial activity as Campaign Trio due to its impersonation of three distinct software brands. Active from February–March 2025, this phase established a baseline operational model of the adversary. This campaign involved a massive number of domains, used an aggressive approach to infrastructure deployment and a clear, focused targeting strategy. The malware distribution strategy of this campaign relied on a vast network of malicious websites that convincingly mimicked legitimate software download portals to lure victims. Between February and March 2025, attackers registered over 2,000 domains, with significant surges in activity in early February and early March. Attackers appear to have automated their domain registration, typically combining the impersonated brand name with a random-looking alphanumeric suffix and using TLDs like .top or .vip. The entire network of over 2,000 domains was hosted on just three IP addresses: 154.82.84[.]227 156.251.25[.]43 156.251.25[.]112 This high-volume domain approach is designed to persist in the face of reputation-based blocking systems. It also ensures that even if some domains are taken down, many other domains remain available. Figure 1 shows a sample attack infrastructure of Campaign Trio including the following info: Three clusters of brand impersonating domains Their association with web server IP addresses An additional server hosting the malware for downloading This centralized model, with over 2,000 domains resolving to just three IP addresses, suggests that attackers viewed components of the infrastructure as disposable. This also implies an aggressive approach to infrastructure deployment that allows the attackers to rapidly establish new websites. The choice of impersonated brands for this campaign reveals a deliberate targeting strategy: i4tools: With over 1,400 domains, this was the most impersonated brand. This is Chinese-language, multi-function software for managing and transferring files to and from Apple-based mobile devices. Youdao: Attackers created over 600 domains to impersonate this popular Chinese dictionary and translation application, strongly indicating a focus on Chinese-speaking users. DeepSeek: We identified only five domains. The impersonation of this AI company demonstrates the attackers' interest in capitalizing on current technology trends. The landing pages hosted on these domains closely mimicked the legitimate sites to deceive victims into downloading the trojanized software installers shown in Figures 2, 3 and 4. Webpages from over 2,000 domains served their malicious payloads from a single source: hxxps[:]//xiazailianjieoss[.]com. This domain hosted ZIP archives containing the trojanized installers. The downloaded archives contained either a malicious Microsoft Installer (MSI) file or a standalone executable. The MSI installers used a custom action to execute a secondary, smaller executable, separating the malicious logic from the main installer to bypass static analysis. MSI-based malware delivery can include a substantial variety of actions also typically executed by benign MSI files. This allows malicious actions to hide within the many legitimate operations generated by an attacker's MSI file. Figure 5 illustrates this concept in action. It shows a malicious MSI sample from Campaign Trio running the embedded malware within the MSI package. Using Microsoft's Orca tool, we can search the malicious MSI file's custom actions for anything suspicious. Running the malicious executable is one of 43 custom actions, not including all the normal actions and processes generated by an MSI file. The MSI file in Figure 5 employs a seemingly legitimate graphical user interface (GUI) for its installation procedure. The Orca tool reveals the MSI file's custom action table, where we've highlighted the malicious action run in the background during the installation. In this instance, the custom action LaunchApplication executes the second-stage malware, a 1.7 MB executable named [System Process]5.exe. Primary functions of [System Process]5.exe are to: Download an obfuscated binary from a staging server Decode the binary and Run it The obfuscated binary was hosted on URLs from fs-im-kefu.7moor-fs1[.]com, a malware distribution point linked to previous Gh0st RAT activity. The deobfuscated binary is the final payload. We identified this final payload as Gh0st RAT, which provides attackers with the following capabilities: Logging keystrokes Capturing screenshots Remote shell access Downloading additional malware These Gh0st RAT samples create scheduled tasks for persistence and use powershell.exe to add exclusions in Windows Defender, so they can run undetected. Once active, these Gh0st RAT samples establish command and control (C2) communication via encrypted TCP traffic over port 8080 to servers with domains like xiaobaituziha[.]com, which resolved to 103.181.134[.]138. We refer to the second campaign as Campaign Chorus because attackers expanded their lures to impersonate over 40 different software applications. Launched in May 2025, this campaign built upon the foundation of the first and showed a significant expansion in targeting. Its TTPs evolved to enhance evasion and bypass security controls. While maintaining a focus on Chinese-speaking users, attackers broadened their lure selection to maximize their potential targets. The attackers organized Campaign Chorus in a more structured manner. In Campaign Chorus, attackers impersonated widely used enterprise messaging software, Chinese versions of secure messaging apps and popular gaming platforms. They also continued targeting software popular with Chinese speakers, such as QQ Music and Sogou browser. This indicates a strategy to reach a wider demographic of Chinese speakers. Figure 6 shows examples of impersonated applications from this campaign. This campaign was initially executed in two distinct waves, distinguished by domain naming conventions and registration dates: Wave 1 (registered May 15, 2025): This wave consisted of 40 domains, all beginning with the prefix guwaanzh Wave 2 (registered May 26–28, 2025): This wave included 51 domains, all starting with the prefix xiazaizhadia The use of structured, wave-based attacks with different domain prefixes and corresponding redirection servers (djbzdhygj[.]com for Wave 1 and yqmqhjgn[.]com for Wave 2) suggests a more organized and possibly experimental approach. The attackers could have been testing the effectiveness of different lures or attempting to compartmentalize their infrastructure to make it more resilient to takedowns. Figure 7 shows an infrastructure map diagram illustrating the two distinct attack waves, their respective redirection servers and how the domains were hosted on a single IP address. Figure 8 shows the most significant advancement during this campaign: adopting a more intricate and elusive infection chain. This multi-stage evolution from the previous campaign increases the complexity of malware embedded in the MSI file. This indicates an increased effort to evade detection. The previous campaign's infection chain was more easily detectable by endpoint detection and response (EDR) solutions. This new chain is explicitly designed to circumvent these protections. In a tactical shift from previous activity, the actor behind Campaign Chorus moved away from a single, self-hosted payload server. Instead, the malicious landing pages used intermediary redirection domains to fetch the malicious ZIP archives from public cloud service buckets. For this tactic, attackers misused cloud services, leveraging trusted reputations to make malicious download traffic appear benign. Consequently, the malicious downloads might bypass network filters that would otherwise block traffic from an unknown or newly registered domain. This also increases the actor's operational resilience, as disrupting a cloud service bucket is a more involved process for defenders than simply blocklisting a malicious IP address. As noted earlier in Figure 8, the core of this new infection chain is an embedded VBScript file run as a custom action by the MSI installer. The VBScript file acts as a file assembler and decryptor for the next-stage malware. This next-stage payload is stored within the MSI file, but not as a single encoded binary. Instead, it is split across multiple data files contained within the MSI's embedded .cab archive. The VBScript file reads these separate components, merges them into a single binary and uses a stored password to decrypt the combined data. This process creates the next-stage malware. This technique is designed to evade static analysis tools that might otherwise detect a single binary containing malicious content within the MSI. The final and most complex step in the infection chain is using DLL side-loading to execute the payload. The VBScript file decodes data binaries within the MSI and saves the resulting two files to disk: The first file is a copy of a legitimate signed executable (wsc_proxy.exe) The second file is a malicious, attacker-crafted DLL named wsc.dll When wsc_proxy.exe is executed, the Windows loader searches for its required dependency, wsc.dll. Because the malicious version is in the same directory, it is loaded into the process memory before the legitimate version in the system directory would be found. This is a classic example of DLL side-loading. It is an evasion technique that allows the attacker's code to run under the guise of a trusted, signed process. The misuse of a legitimate executable is meant to bypass application allow-listing and process-based monitoring. The parent process initiating the malicious activity is itself benign and digitally signed by a reputable vendor. This makes it significantly harder for security tools to flag the activity as malicious. When analyzed together, the evidence from Campaign Trio and Campaign Chorus reveals a consistent operational playbook, allowing us to build a distinct behavioral profile. The technical differences are best understood not as the work of two unrelated campaigns, but as the logical evolution of a single group adapting its methods. The campaigns have several key characteristics that form a strategic signature: Mass-scale programmatic infrastructure: Both campaigns rely on the programmatic generation of domains for brand impersonation using a consistent naming convention. Specific demographic focus: Both campaigns focus heavily on software popular with Chinese-speaking users, even when deploying infrastructure in regions like the U.S. and Singapore. This indicates an actor with a deep and specific understanding of this demographic, rather than an opportunistic actor casting a wide, generic net. “Burn-and-churn” operational tempo: Both campaigns use a centralized and disposable infrastructure model. The strategy of hosting thousands of domains on a handful of IP addresses demonstrates a rapid deployment approach where the attackers consider the infrastructure expendable. The actor prioritizes the speed and scale of deployment over stealth and long-term resilience. They are confident in their ability to quickly pivot to new domains and servers. Two-tiered infrastructure: The actor exhibits a clear separation between its disposable, high-volume access infrastructure (the thousands of impersonation domains) and its more critical operational infrastructure (the payload and C2 servers). While the access layer is designed to be burned, the operational layer shows evolution (from self-hosted to cloud-hosted) aimed at increasing longevity and resilience. This architectural choice allows the actor to absorb the loss of their frontend domains without losing its core payload delivery and C2 capabilities. Table 1 shows the adversary's methods mapped to the MITRE ATT&CK framework, providing a standardized view of its operational tactics. Table 1. TTP profile summary (MITRE ATT&CK mapping). The results of our investigation reinforce that these campaigns are not isolated, short-term events. Attackers are actively maintaining and expanding their infrastructure, indicating a persistent, long-term operation. We investigated the WHOIS creation dates of domains associated with both these campaigns and found that they have consistently registered domains from February–August 2025. Our analysis showed a significant surge in activity between February and May 2025. During these four months, attackers created over 2,500 domains, accounting for 87.4% of all malicious domains identified in connection with these campaigns. Figure 9 shows the distribution of domains belonging to these campaigns created per week according to their WHOIS creation dates. In February and March of 2025, we observed over 1,500 domains belonging to the first campaign being registered. We also noticed an interesting pattern where attackers registered between 100-200 domains every week for a month. This pattern started with 100 domains registered on April 15, 2025. This was followed by 237 more in the week of April 21–27, the majority of which were registered on April 22. This was followed by another 191 domains between April 28–May 4. Of these, 104 were registered on April 29. This was followed by a week of low activity (around May 5, 2025) and ended with almost 261 domains registered between May 13–15, 2025. This regularity suggests an automated or highly structured process for routine infrastructure replenishment, likely to replace domains that have been blocked during operations. From the pDNS data, we find that these new domains are pointed to the same core IP addresses used in both campaigns, with activity observed as recently as July 2025. Domains associated with the first campaign's infrastructure continue to resolve to 156.251.25[.]112. For example, we observed domains such as youdaxxyzr[.]top and i4toolscacsm[.]top actively resolving to this IP address. This demonstrates that the actor did not simply abandon its initial core IP address infrastructure but continued to leverage the IP address for ongoing attacks. Similarly, the infrastructure for the second campaign remains active. The IP address 95.173.197[.]195 continues to serve new malicious domains as of early October 2025. Continuously registering and refreshing domains is a clear tactic to evade blocklists. It helps ensure the longevity of the campaigns, pointing to a well-resourced and determined adversary. Figure 10 depicts a graph of the first campaign. It shows domains involved in both campaigns. Both campaigns use the same elements, like nameservers and hosting IP addresses. This graph depicts 683 domains that share the same set of nameservers and resolve to the same hosting IP address 156.251.25[.]112. This IP address is geolocated to Hong Kong. Furthermore, we analyzed pDNS query volumes for domains associated with the first campaign to quantify its sustained activity over time. We found that while daily query volumes fluctuated, there was a gradual upward trend in queries toward domains associated with this campaign between March 2025 and July 2025. Figure 11 shows a large peak in the number of queries toward these domains on July 12, 2025. We investigated domains contributing to this peak, and over 68% of these queries were generated for domains registered between March 6 and March 13, 2025, representing an exact four-month gap. This increase in query volume could be due to changes in the attackers' content or their connections to other entities. The parallel operation of both old and new infrastructure through sustained activity suggests an operation that is not merely evolving but consists of multiple infrastructures and distinct tool sets simultaneously. This could indicate A/B testing of TTPs, targeting different victim sets with different levels of complexity, or simply a cost-effective strategy of continuing to leverage older assets as long as they remain effective. The campaigns detailed in this article represent a persistent, large-scale and evolving threat. Operating at scale combined with a continuous adaptation of TTPs presents a significant challenge for defenders. There is a clear evolution in these two campaigns. Campaign Trio, the first campaign, uses direct droppers. Campaign Chorus, the second campaign, leverages a more complex multi-stage infection chain and uses DLL sideloading. The following traits are notable: Consistent focus on a Chinese-speaking demographic Programmatically generating thousands of domains Strategically using both self-hosted and major cloud provider infrastructure This signals a broader trend where threat actors will increasingly leverage legitimate cloud services and signed software, shifting the defensive focus from blocking known-bad indicators to detecting sophisticated behavioral anomalies. Palo Alto Networks customers are better protected from the threats discussed above through the following products: The Advanced WildFire machine-learning models and analysis techniques have been reviewed and updated in light of the indicators shared in this research. Advanced URL Filtering and Advanced DNS Security identify known domains and URLs associated with this activity as malicious. Advanced Threat Prevention has an inbuilt machine learning-based detection that can detect exploits in real time. Cortex XDR and XSIAM are designed to prevent the execution of known malicious malware, and also prevent the execution of unknown malware using Behavioral Threat Protection and machine learning based on the Local Analysis module. Cortex Cloud DSPM can help organizations detect if their cloud infrastructure has been used to host malicious binaries like those described in this article by routinely scanning cloud storage containers and properly classifying the data within. - This functionality can assist organizations from unwittingly being used to host malicious binaries placed by threat actors. - While the nature of the article does not point to the compromise of victim cloud environments to host these binaries, Cortex Cloud DSPM can detect malicious data and prevent it from harming the organization itself or, in this case, external organizations. If you think you may have been compromised or have an urgent matter, get in touch with the Unit 42 Incident Response team or call: North America: Toll Free: +1 (866) 486-4842 (866.4.UNIT42) UK: +44.20.3743.3660 Europe and Middle East: +31.20.299.3130 Asia: +65.6983.8730 Japan: +81.50.1790.0200 Australia: +61.2.4062.7950 India: 00080005045107 Palo Alto Networks has shared these findings with our fellow Cyber Threat Alliance (CTA) members. CTA members use this intelligence to rapidly deploy protections to their customers and to systematically disrupt malicious cyber actors. Learn more about the Cyber Threat Alliance. A comprehensive list of IoCs associated with these campaigns can be found in the tables below. Campaign Trio IoCs Campaign Chorus IoCs Observed Domain Activity (Based on pDNS Data) The authors would like to thank Shehroze Farooqi, Bradley Duncan and Alex Starov for their valuable insights and feedback to improve the research work mentioned in this article. Trojanized Installer Distribution Campaign – Unit 42, Palo Alto Networks Legitimate Software Impersonation Campaign – Unit 42, Palo Alto Networks Ghost RAT (Malware Family) - Malpedia Gh0st RAT: malware active for 15 years is still used by threat operators – Side Channel Blog 7m-sdk.7moor-fs1.com URL Report – IBM X-Force Exchange Behind the Great Wall Void Arachne Targets Chinese-Speaking Users – TrendMicro Malware Campaigns Targets Chinese Speaking Users With Fake Installers – DigiAlert Musical Chairs: A Multi-Year Campaign Involving a New Variant of Gh0st Malware – Unit 42, Palo Alto Networks
unit42.paloaltonetworks.comNov 14, 2025extracted
Trend Micro Awards Over $1,000,000 to Ethical Hackers
Stay connected with press releases from Trend teams in your region. Participants at Pwn2Own Ireland discovered scores of zero-day vulnerabilities DALLAS, Oct. 27, 2025 /PRNewswire/ -- Trend Micro Incorporated (TYO: 4704; TSE: 4704), a global cybersecurity leader, today celebrated the efforts of the global security research community at Pwn2Own Ireland. Contestants discovered and disclosed 73 unique zero-day vulnerabilities in printers, network storage systems, smart home devices, surveillance equipment, home networking equipment, flagship smartphones, and wearable technology. To learn more about Pwn2Own Ireland 2025, please visit: https://www.zerodayinitiative.com/blog/2025/10/23/pwn2own-ireland-2025-day-three-and-master-of-pwn Rachel Jin, Chief Platform and Business Officer at Trend: "Our mission is to approach security proactively and gather the deepest threat intelligence in the industry. The 73 zero-day bugs discovered at Pwn2Own will directly help make the digital world a safer place. We're proud to empower vendors to patch these vulnerabilities while offering our customers protection from exploits well ahead of any other cybersecurity provider. As cyber risk continues to rise worldwide, Pwn2Own remains a valuable tool in staying ahead." A total of $1,024,750 in prizes were awarded to the participants. Research conducted at Pwn2Own enables Trend to protect customers from zero-day exploits an average of 71 days ahead of the industry, an essential advantage in the race against cybercriminals. The event featured a variety of highlights as hackers competed for a cash prize pool of over $2 million: The next competition, Pwn2Own Automotive, will be held in Tokyo, Japan on January 21-23, 2026. About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information between people, governments, and enterprises. Trend leverages security expertise and AI to protect more than 500,000 enterprises and millions of individuals across clouds, networks, endpoints, and devices worldwide. At the core is Trend Vision One™, the only AI-powered enterprise cybersecurity platform that centralizes cyber risk exposure management and security operations, delivering layered protection across on-premises, hybrid, and multi-cloud environments. The unmatched threat intelligence delivered by Trend empowers organizations to proactively defend against hundreds of millions of threats every day. Proactive security starts here. TrendMicro.com SOURCE Trend Micro Incorporated
newsroom.trendmicro.comOct 27, 2025extracted
Optimize security operations with AWS Security Incident Response
Optimize security operations with AWS Security Incident Response July 6, 2026: We updated this post to reflect current feature capabilities. Security threats demand swift action, which is why AWS Security Incident Response delivers protection that can immediately strengthen your security posture. This comprehensive solution combines automated triage and evaluation logic with your security perimeter metadata to identify critical issues, seamlessly bringing in human expertise when needed. When Security Incident Response is integrated with Amazon GuardDuty and AWS Security Hub within a unified security environment, organizations gain 24/7 access to AWS security incident response professionals for rapid detection, expert analysis, and efficient threat containment—managed through one intuitive console. AWS Security Incident Response is included with AWS Enterprise Support and AWS Unified Operations, which helps organizations adopt and operate AWS at scale efficiently and securely. In this post, we guide you through enabling Security Incident Response and executing a proof of concept (POC) to quickly enhance your security capabilities while realizing immediate benefits. We explore the service’s functionality, establish POC success criteria, define your configuration, prepare for deployment, enable the service, and optimize effectiveness from day one, helping your organization build confidence throughout the incident response lifecycle while improving recovery time. Understanding the functionality of Security Incident Response AWS Security Incident Response service provides comprehensive threat detection and response capabilities through a streamlined four-step process. It begins by ingesting security findings from GuardDuty and select Security Hub Cloud Security Posture Management (CSPM) integrations with third-party tools. The service then automatically triages these findings using customer metadata and threat intelligence to identify anomalous behavior and suspicious activities. When potential threats are detected, Security Incident Response team responders proactively investigate cases through the customer portal to determine whether they are true or false positives. For confirmed threats, the service escalates findings for immediate action, while false positives trigger updates to the auto-triage system and suppression rules for GuardDuty and Security Hub, continuously improving detection accuracy. Comprehensive protection with minimal prerequisites Security Incident Response delivers powerful security capabilities through seamless integration with both the threat detection and incident response (TDIR) system and third-party security services such as CrowdStrike, Lacework, TrendMicro, SentinelOne, Palo Alto Networks – Prisma Cloud Compute, and Wiz (Toxic Combinations). This solution provides a unified command center for end-to-end incident management—from planning and communication to resolution—while ingesting GuardDuty findings and integrating with external providers through Security Hub CSPM. For third-party integrations, only finding ingestion is required—not the full Security Hub CSPM feature set (no security standards, controls, or compliance checks needed). The first 10,000 findings per month do not incur any costs, then cost $0.00003 per finding thereafter (for example, 610,000 findings cost about $18 per month). For more information, see Security Hub CSPM pricing. With secure case management and an immutable activity timeline, it significantly enhances your security operations by augmenting your security operations center (SOC) and incident response (IR) teams with improved visibility and access to AWS-proven tools and personnel. AWS security incident response personnel work collaboratively with your responders during investigations and recovery, freeing your valuable resources for other priorities. The service delivers continuous value through proactive monitoring and response capabilities. It constantly monitors your environment using GuardDuty and Security Hub findings, with service automation, triage, and analysis working diligently in the background to alert you only for genuine security concerns. This protection provides immediate value during potential incidents without demanding your constant attention. Getting started is straightforward—the only prerequisite is having AWS Organizations enabled and making sure that you have established Organizations with a fundamental organizational unit (OU) structure encompassing member accounts. This foundation not only enables Security Incident Response deployment but also serves as the cornerstone for implementing a robust TDIR strategy across your organization. Determine success criteria Establishing success criteria helps benchmark the outcomes of the POC with the goals of the business. Some example criteria include: Designate an incident response team: Identity and document internal team members and external resources responsible for incident response. As highlighted in AWS Well-Architected Security Pillar, having designated personnel reduces triage and response times during security incidents. Develop a formal incident response framework: Develop a comprehensive incident response plan with detailed playbooks and regular table-top exercise protocols. AWS provides a reference library of playbooks on GitHub. Run tabletop exercises: Consider implementing regular simulations that test incident response plans, identify gaps, and build muscle memory across security teams before a real crisis occurs. AWS provides context on various types of tabletop exercises. Identify existing third-party security providers: Identify third-party security providers with Security Hub integrations that feed into Security Incident Response. AWS partners provide findings as documented at Detect and Analyze. Implement GuardDuty: Configure GuardDuty according to best practices to monitor and detect threats across critical services. AWS maintains GuardDuty best practices in AWS Security Services Best Practices for GuardDuty. Review your success criteria to make sure that your goals are realistic given your timeframe and potential constraints that are specific to your organization. For example, do you have full control over the configuration of AWS services that are deployed in an organization? Do you have resources that can dedicate time to implement and test? Is this time convenient for relevant stakeholders to evaluate the service? Define your Security Incident Response configuration After establishing your success criteria and timeline, it’s best practice to define your Security Incident Response configuration. Some important decisions include the following: Select a delegated administrator account: Identify which account will serve as delegated administrator (DA) for Security Incident Response. This account and the AWS Region you select will host the Security Incident Response service and portal. AWS Security Reference Architecture (AWS SRA) recommends using dedicated security tooling account. Review the considerations and recommendations documentation before finalizing the DA. Define the account scope: Security Incident Response is considered an organization-level service. Every account in every Region within your organization is entitled to coverage under a single subscription. Service coverage automatically adjusts as accounts are added or removed, providing complete protection across your entire AWS footprint. Configure findings sources: Determine which security findings meet your organization’s needs. The service automatically ingests GuardDuty findings organization-wide and select Security Hub finding types from third-party partners. Evaluate which GuardDuty protection plans and Security Hub findings provide the most value for your security posture and incident response capabilities. Develop an escalation framework: Establish clear escalation thresholds for different case types: self-managed, AWS-supported, and proactive cases. Define who has authority to determine case submission and type based on severity, impact, and resource requirements. Implement analytics strategy: Determine whether to use native AWS analytics tools (such as Amazon Athena, Amazon OpenSearch, and Amazon Detective) or integrate with existing security information and event management (SIEM) solutions. These capabilities can enrich incident response with contextual data and deeper insights. Prepare for deployment After determining success criteria and Security Incident Response configuration, identify stakeholders, desired state, and timeframe. Prepare for deployment by completing: Project plan and timeline: Develop a project plan with defined success criteria, scope boundaries, key milestones, and realistic implementation timelines. Suggested timeline of events: - Before enablement: Configure GuardDuty, and optionally Security Hub third parties, perform resource planning - Day 0 – Enable the service - Week 1 – Open reactive security incident response cases - Week 2 – Connect to IT service management (ITSM) tools - Week 3 – Execute a tabletop exercise - Week 4 – Review the reporting provided from the service Identify stakeholders: Identify CISO, information security teams, SOC personnel, incident response teams, security engineers, finance, legal, compliance, external MSSPs, and business unit representatives. Develop a RACI matrix: Create detailed RACI chart defining roles and responsibilities across incident response lifecycle, facilitating accountability and proper communication channels. Configure management account access: Secure authorization to delegate administrative access. For more information, see Permissions required to designate a delegated Security Incident Response administrator account. Set up IAM roles and permissions: Use AWS Identity and Access Management (IAM) roles to implement role-based access controls aligned with the RACI chart, including case management, escalation, and read-only roles using AWS managed policies. For more information, see AWS Managed Policies. Enable Security Incident Response With preparations in place, you are ready to enable the service. Access Security Incident Response in the management account: Within the organization’s management account, go to the AWS Management Console and search for Security Incident Response in the console search bar. Choose Sign Up. Verify that Use delegated administrator account – Recommended is selected, enter the delegated administrator account number in the Account ID field and choose Next. Sign in to the delegated administrator account configured in step 3, search for Security Incident Response, and choose Sign up. Complete setup in the delegated administrator account: Define membership details: - Select your home region under Region selection. - For Membership name, enter a suitable name that follows your organization’s naming standards. - Under Membership contacts, enter the Primary and Secondary contact information. Add Membership tags according to your organization’s tagging strategy. Choose Next. Configure permissions: - Select By choosing this option…, then choose Next. - Review service permissions and choose Next. Review the membership configuration and details, then choose Sign up. Note: Detailed instructions can be found in the YouTube setup video. Many organizations have well-established processes and application suites for IR and security threat management. To accommodate these pre-existing setups, AWS has developed integrations with popular ITSM and case management applications. AWS Security Incident Response enables bi-directional integration with Jira and ServiceNow (case updates are synced in both directions), and event-driven integrations with Slack and PagerDuty through Amazon EventBridge—with more on the way. We have provided comprehensive instructions to guide you through the setup process in GitHub. Optimize value on day one Immediately after enabling the service, Security Incident Response begins to ingest your GuardDuty findings—and Security Hub CSPM findings from security partners if you’ve configured them. Your findings are automatically triaged and monitored using deterministic evaluation logic; based on your organization’s unique metadata and security perimeter, high-priority threats are escalated to your Security Incident Response command center for immediate investigation. While your organization receives 24/7 coverage from the start, implementing these recommended optimizations will significantly enhance threat detection accuracy, reduce false positives, accelerate response times, and strengthen your overall security posture through customized protection aligned with your specific business risks and compliance requirements. To maximize immediate value from Security Incident Response, we suggest using its reactive capabilities beginning on day one. When your team encounters suspicious activities or requires expert investigation, you can create an AWS-supported case through the service portal to engage AWS security incident responders directly. These security experts effectively extend your team’s capabilities, providing specialized knowledge and guidance to help you quickly understand, contain, and remediate potential security concerns. This on-demand access to AWS security incident response can reduce your mean time to resolution, minimize potential impact, and make sure you have professional support even for complex security scenarios that might otherwise overwhelm internal resources. Examples of reactive support queries include: We noticed a suspicious IP address in our environment, performing various API calls. Can you help us investigate? A new account was created two days ago, we were notified through an Amazon EventBridge rule and our endpoint detection and response (EDR) integrations, can you help us scope it and find out who created it? How was it created? An AWS Identity and Access Management (IAM) user is making cross-Region API calls and creating resources in an unused Region. Our EDR solution detected unusual behavior on our production website, indicating a potential breach. Our EDR detected a suspicious web-shell upload and activity. We need help investigating and isolating this. An unauthorized user generated API activity above their authorization level, help us find privilege escalations. We need help analyzing security logs from our AWS WAF and Amazon Elastic Compute Cloud (Amazon EC2) instances. Are there any Indicators of compromise or suspicious patterns? Next steps If you decide to move forward with AWS Security Incident Response and deploy a POC, we recommend the following action items: Configure and deploy GuardDuty to help maintain comprehensive and relevant coverage across your management and member accounts, critical services, and workloads. Verify that third-party security tools (such as CrowdStrike, Lacework, or Trend Micro) are properly integrated with Security Hub. Communicate the security incident response tooling changes to the relevant organizational teams. Conclusion In this post, we showed you how to plan and implement an AWS Security Incident Response POC. You learned how to do so through phases, including defining success criteria, configuring Security Incident Response, and validating that Security Incident Response meets your business needs. As a customer, this guide will help you run a successful POC with Security Incident Response. It guides you in assessing the value and factors to consider when deciding to implement the current features. Additional resources AWS Security Incident Response – Getting started Configuring security tool integrations through Security Hub Managing Security Incident Response events with Amazon EventBridge Amazon GuardDuty best practices AWS Security Hub best practices AWS Security Incident Response Technical Guide (best practices) AWS Managed Services Offering AWS Security Incident Response Blog: The customer’s journey to accelerating the incident response lifecycle If you have feedback about this post, submit comments in the Comments section below. If you have questions about this post, contact AWS Support.
aws.amazon.comSep 23, 2025extracted
Trend Micro Unmasks Global "Task Scam" Industry
Stay connected with press releases from Trend teams in your region. New research exposes operations behind deceptive digital job platforms and highlights growing financial and psychological harm to victims DALLAS, Aug. 19, 2025 /PRNewswire/ -- Trend Micro Incorporated (TYO: 4704; TSE: 4704), a global leader in cybersecurity, today released new research revealing the mechanics and scale of a rapidly growing fraud model known as "task scams": sophisticated online job scams that lure victims into repetitive digital tasks and systematically strip them of funds through escalating deposit demands. To read the full report, Unmasking Task Scams, visit: https://www.trendmicro.com/vinfo/us/security/news/cybercrime-and-digital-threats/unmasking-task-scams-to-prevent-financial-fallout-from-fraud Robert McArdle, Director of Forward Threat Research at Trend: "Task scams are now one of the most financially and psychologically damaging cybercrime threats individuals face today. The infrastructure enabling them, from domain registrars to SMS blasting services, requires immediate attention. Meanwhile, organizations can reduce risk by making their recruitment practices transparent and educating job seekers on how to identify legitimate communications." Trend™ Research uncovers a sprawling global criminal infrastructure that impersonate legitimate companies, exploit trusted communications channels, and prey on job seekers using gamification techniques. Trend reports that scammers are transferring millions via cryptocurrency wallets, with victims losing between hundreds and hundreds of thousands of dollars each. Modern scam tactics are highly targeted and designed to go undetected. In a recent global study of over 6,500 consumers conducted by Trend, 39% reported becoming aware of being a scam victim only after losing a significant amount of money. The report includes firsthand engagements with scammers, infrastructure mapping of malicious websites, and forensic analysis of associated cryptocurrency wallets. In one case, a single wallet received over US $187,000 in less than two months. Another wallet was linked to more than US $1.2 million in transactions. Key findings include: Victims report a high emotional toll, often describing behaviors akin to gambling addiction. In some cases, task scams are linked to larger criminal operations that include forced scam labor and human trafficking in Southeast Asia, though such ties are not confirmed in every case. Using Trend Micro ScamCheck with Scam Radar can help users recognize early on when they are being targeted by a scammer. An industry first, Scam Radar offers real-time protection by identifying scam tactics utilized by cybercriminals as they happen, alerting users and empowering them to take action before any harm is done. The latest version of Trend Micro ScamCheck is available on the Apple App Store and Google Play. About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information. Fueled by decades of security expertise, global threat research, and continuous innovation, Trend Micro's AI-powered cybersecurity platform protects hundreds of thousands of organizations and millions of individuals across clouds, networks, devices, and endpoints. As a leader in cloud and enterprise cybersecurity, Trend's platform delivers a powerful range of advanced threat defense techniques optimized for environments like AWS, Microsoft, and Google, central visibility for better, faster detection and response. With 7,000 employees across 70 countries, Trend Micro enables organizations to simplify and secure their connected world. www.TrendMicro.com. SOURCE Trend Micro Incorporated
newsroom.trendmicro.comAug 19, 2025extracted
Trend Micro Warns of Thousands of Exposed AI Servers
Stay connected with press releases from Trend teams in your region. Latest research reveals mounting infrastructure-level risks from diverse components DALLAS, July 29, 2025 /PRNewswire/ -- Trend Micro Incorporated (TYO: 4704; TSE: 4704), a global cybersecurity leader, today urged AI engineers and IT leaders to heed best practices in developing and deploying secure systems, or risk exposure to data theft, poisoning, ransom, and other attacks. To learn more about how network defenders and adversaries are using AI, read Trend Micro State of AI Security Report, 1H 2025: https://www.trendmicro.com/vinfo/us/security/news/threat-landscape/trend-micro-state-of-ai-security-report-1h-2025 Rachel Jin, Chief Enterprise Platform Officer at Trend: "AI may represent the opportunity of the century for global businesses. But those rushing in too fast without taking adequate security precautions may end up causing more harm than good. As our report reveals, too much AI infrastructure is already being built from unsecured and/or unpatched components, creating an open door for threat actors." Trend's report highlights several AI-related security challenges: 1) Vulnerabilities/exploits in critical components Organizations wishing to develop, deploy and use AI applications must leverage multiple specialized software components and frameworks, which may contain vulnerabilities one may find in regular software. The report reveals zero-day vulnerabilities and exploits in core components including ChromaDB, Redis, NVIDIA Triton, and NVIDIA Container Toolkit. 2) Accidental exposure to the internet Vulnerabilities are often the result of rushed development and deployment timelines, as are instances when AI systems are accidentally exposed to the internet, where they can be probed by adversaries. As detailed in the report, Trend has found 200+ ChromaDB servers, 2,000 Redis servers, and 10,000+ Ollama servers exposed to the internet with no authentication. 3) Vulnerabilities in open-source components Many AI frameworks and platforms use open-source software libraries to provide common functionality. However, open-source components often contain vulnerabilities that end up creeping into production systems, where they are hard to detect. At the recent Pwn2Own Berlin, which featured a new AI category, researchers uncovered an exploit for the Redis vector database, which stemmed from an outdated Lua component. 4) Container-based weaknesses A great deal of AI infrastructure runs on containers, meaning it is exposed to the same security vulnerabilities and threats that impact cloud and container environments. As outlined in the report, Pwn2Own researchers were able to uncover an exploit for the NVIDIA Container Toolkit. Organizations should sanitize inputs and monitor runtime behavior to mitigate such risks. Stuart MacLellan, CTO, NHS SLAM: "There are still lots of questions around AI models and how they could and should be used. We now get much more information now than we ever did about the visibility of devices and what applications are being used. It's interesting to collate that data and get dynamic, risk-based alerts on people and what they're doing depending on policies and processes. That's going to really empower the decisions that are made organizationally around certain products." Both the developer community and its customers must better balance security with time to market in order to mitigate the risks outlined above. Concrete steps could include: About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information. Fueled by decades of security expertise, global threat research, and continuous innovation, Trend Micro's AI-powered cybersecurity platform protects hundreds of thousands of organizations and millions of individuals across clouds, networks, devices, and endpoints. As a leader in cloud and enterprise cybersecurity, Trend's platform delivers a powerful range of advanced threat defense techniques optimized for environments like AWS, Microsoft, and Google, and central visibility for better, faster detection and response. With 7,000 employees across 70 countries, Trend Micro enables organizations to simplify and secure their connected world. www.TrendMicro.com. SOURCE Trend Micro Incorporated
newsroom.trendmicro.comJul 29, 2025extracted
AI-Generated Media Drives Real-World Fraud, Identity Theft, and Business Compromise
Stay connected with press releases from Trend teams in your region. Trend Micro uncovers the criminal playbook for deepfake-enabled cybercrime DALLAS, July 9, 2025 /PRNewswire/ -- Trend Micro Incorporated (TYO: 4704; TSE: 4704), a global cybersecurity leader, today released a new report exposing the scale and maturity of deepfake-enabled cybercrime. As generative AI tools become more powerful, affordable, and accessible, cybercriminals are rapidly adopting them to support attacks, ranging from business fraud to extortion and identity theft. To read the full report, Deepfake it 'til You Make It: A Comprehensive View of the New AI Criminal Toolset, please visit: https://www.trendmicro.com/vinfo/us/security/news/cybercrime-and-digital-threats/deepfake-it-til-you-make-it-a-comprehensive-view-of-the-new-ai-criminal-toolset The report shows how deepfakes have moved beyond hype into real-world exploitation, undermining digital trust, exposing companies to new risks, and accelerating the business models of cybercriminals. David Sancho, senior threat researcher at Trend: "AI-generated media is not just a future risk, it's a real business threat. We're seeing executives impersonated, hiring processes compromised, and financial safeguards bypassed with alarming ease. This research is a wake up call—if businesses are not proactively preparing for the deepfake era, they're already behind. In a world where seeing is no longer believing, digital trust must be rebuilt from the ground up." The research found that threat actors no longer need underground expertise to launch convincing attacks. Instead, they are using off-the-shelf video, audio, and image generation platforms, many of which are marketed to content creators, to generate realistic deepfakes that deceive both individuals and organizations. These tools are inexpensive, easy to use, and increasingly capable of bypassing identity verification systems and security controls. The report outlines a growing cybercriminal ecosystem where these platforms are used to execute convincing scams, including: The criminal underground is actively trading tutorials, toolkits, and services to streamline these operations. From step-by-step playbooks for bypassing onboarding procedures to plug-and-play face-swapping tools, the barrier to entry is now minimal. As deepfake-enabled scams grow in frequency and complexity, businesses are urged to take proactive steps to minimize their risk exposure and protect their people and processes. This includes educating staff on social engineering risks, reviewing authentication workflows, and exploring detection solutions for synthetic media. About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information. Fueled by decades of security expertise, global threat research, and continuous innovation, Trend Micro's AI-powered cybersecurity platform protects hundreds of thousands of organizations and millions of individuals across clouds, networks, devices, and endpoints. As a leader in cloud and enterprise cybersecurity, Trend's platform delivers a powerful range of advanced threat defense techniques optimized for environments like AWS, Microsoft, and Google, and central visibility for better, faster detection and response. With 7,000 employees across 70 countries, Trend Micro enables organizations to simplify and secure their connected world. www.TrendMicro.com. SOURCE Trend Micro Incorporated
newsroom.trendmicro.comJul 9, 2025extracted
AI on the Frontline: Global Firms Back Innovation, Brace for New Cyber Threats
Stay connected with press releases from Trend teams in your region. New Trend Micro research reveals widespread AI adoption in cybersecurity strategies, but mounting concerns cyber risk exposure DALLAS, July 1, 2025 /PRNewswire/ -- Global AI cybersecurity leader Trend Micro Incorporated (TYO: 4704; TSE: 4704) published new research* today revealing that while organizations are embracing artificial intelligence to strengthen their cyber defenses, many are increasingly concerned about the technology's potential to expand their attack surface and introduce new risks. To learn more about Trend's latest research, visit: https://www.trendmicro.com/explore/aichangingcyberrisk Rachel Jin, Chief Enterprise Platform Officer at Trend: "AI holds enormous promise for strengthening cyber defenses, from identifying anomalies faster to automating time-consuming tasks. But attackers are just as eager to leverage AI for their own purposes, and that creates a rapidly shifting threat landscape. Our research and real-world testing make it clear that security must be built into AI systems from the outset. There is simply too much at stake to treat this as an afterthought." According to the study, 81% of global businesses are already using AI-driven tools as part of their cybersecurity strategy, with a further 16% actively exploring implementation. Nearly all respondents (97%) are open to using AI in some capacity. Over half are already relying on it for essential processes such as automated asset discovery, risk prioritization and anomaly detection. AI and automation are now considered top priorities for improving cybersecurity over the next 12 months by 42% of surveyed organizations. This optimism also comes with significant risk. An overwhelming 94% of businesses believe that AI will negatively impact their cyber risk exposure within the next three to five years. Over half expect a surge in the scale and complexity of AI-driven attacks, which they say will force them to rethink and reshape existing cybersecurity strategies. Many point to the risk of sensitive data exposure, uncertainty around how data is processed and stored by AI systems, the potential for proprietary data to be exploited by untrusted models, as well as increased compliance pressures and monitoring challenges stemming from a proliferation of new endpoints, APIs and shadow IT. The tension between opportunity and risk was evident at Trend's Pwn2Own event in Berlin, where the AI category was introduced for the first time. The results offered a compelling snapshot of where AI security currently stands. Twelve entries targeted four major AI frameworks, with the NVIDIA Triton Inference Server receiving the most attention. Chroma, Redis, and the NVIDIA Container Toolkit were also successfully exploited, in some cases using just a single bug to achieve full compromise. In total, seven unique zero-day vulnerabilities were uncovered in the AI frameworks. The vendors now have 90 days to patch the flaws before technical details are made public. As AI becomes more deeply integrated in enterprise IT environments, Trend urges security leaders to proactively evaluate the evolving risk landscape and embed rigorous security practices into every stage of AI adoption. *Trend Micro commissioned Sapio Research to interview 2250 individuals with responsibility for IT and/or cybersecurity—across multiple verticals, organization sizes and 21 countries in Europe, North America and APAC. About Trend Micro Trend Micro, a global cybersecurity leader, helps make the world safe for exchanging digital information. Fueled by decades of security expertise, global threat research, and continuous innovation, Trend Micro's AI-powered cybersecurity platform protects hundreds of thousands of organizations and millions of individuals across clouds, networks, devices, and endpoints. As a leader in cloud and enterprise cybersecurity, Trend's platform delivers a powerful range of advanced threat defense techniques optimized for environments like AWS, Microsoft, and Google, and central visibility for better, faster detection and response. With 7,000 employees across 70 countries, Trend Micro enables organizations to simplify and secure their connected world. www.TrendMicro.com. SOURCE Trend Micro Incorporated
newsroom.trendmicro.comJul 1, 2025extracted