N4D Mesh Controller is an active Linux malware campaign that exploits exposed MCP servers and other internet-facing services to steal credentials, move laterally, persist, and maintain command-and-control. Datadog Security Research confirmed a newer loader-to-agent chain, rotated infrastructure, and direct runtime evidence that the 33.8-go-titan agent enumerates MCP tools, invokes execute_command, and reports results back to its controller. #N4D #MCP #33.8-go-titan #cdnorigin.net #209.99.186.235
Keypoints
- N4D targets publicly reachable Model Context Protocol (MCP) servers and other exposed services as initial access points.
- The campaign automates MCP discovery by requesting tools/list, classifying tools, and invoking dangerous capabilities such as execute_command.
- Datadog observed a newer loader contacting 209.99.186.235 and retrieving a second-stage agent identifying as 33.8-go-titan.
- The malware includes broad exploitation paths for databases, containers, Kubernetes, Jenkins, Ray, LightLLM, and other infrastructure.
- Persistence methods include hidden cron jobs, shell profile modification, systemd units, SSH key installation, and execution from temporary or memory-backed directories.
- The agent also uses controller APIs with custom headers and can launch Cloudflare Quick Tunnels as an additional channel.
- Runtime analysis showed the agent making thousands of connection attempts across hundreds of destination IPs, confirming broad multi-service scanning.
MITRE Techniques
- [T1190] Exploit Public-Facing Application â Used against exposed MCP servers and other internet-facing services as entry points into the environment (âturns exposed Model Context Protocol (MCP) serversâŚinto entry pointsâ).
- [T1105] Ingress Tool Transfer â Retrieves architecture-specific agents and loaders with curl/wget from remote infrastructure (âdownload an architecture-specific agent from cdnorigin.net, 209.99.186.73, orâŚ209.99.186.235â).
- [T1059.004] Unix Shell â Shell scripts and watchdogs use shell interpreters, setsid, and command execution during delivery and persistence (âshell scripts and loaders use curl or wgetâ).
- [T1053.003] Cron â Establishes persistence through hidden cron entries and cron.d files (âhidden cron entriesâ, â/etc/cron.d/.sys-healthâ).
- [T1543.002] Systemd Service â Installs a systemd unit for persistence (â/etc/systemd/system/sys-resource.serviceâ).
- [T1098.004] SSH Authorized Keys â Adds an SSH public key to maintain access (âinstalled into /root/.ssh/authorized_keysâ).
- [T1055] Process Injection â Not directly shown as injection, but the agent executes from memory-backed locations and disguises processes to blend in (âexecution from memory-backed directoriesâ, âprocess names that mimic Linux kernel workersâ).
- [T1036] Masquerading â Uses kernel-worker-style names and hidden dotfiles to conceal malicious activity (âprocess names that mimic Linux kernel workersâ).
- [T1021] Remote Services â Expands laterally to services such as SSH, databases, Docker, Kubernetes, and application servers (âtargeting SSH, databases, container APIs, Kubernetesâ).
- [T1219] Remote Access Software â Uses controller APIs and tasking channels for remote control (â/api/register, /api/beacon, /api/task/, /api/result/, /api/ptyâ).
- [T1562.001] Disable or Modify Tools â Restricts or alters host visibility by removing or changing startup and watchdog artifacts (âwatchdog scriptsâ, âshell-profile modificationâ).
- [T1041] Exfiltration Over C2 Channel â Sends intelligence and tool results back to the controller (âreports the result to its controllerâ, âsent health and host intelligenceâ).
- [T1132.001] Standard Encoding â Uses custom header-based authentication and structured API communication (âauthenticated with custom X-Mesh-Auth and X-Operator-Key headersâ).
- [T1595] Active Scanning â Performs broad scanning across many IPs and ports (â22,831 connection attempts across 742 destination IPsâ).
- [T1021.001] Remote Services: Remote Desktop Protocol â Not explicitly mentioned; omitted from listing because not supported by the article.
Indicators of Compromise
- [IPv4] Controller / payload delivery infrastructure â 209.99.186.235, 209.99.186.73, and other observed operator IPs
- [Domain] Delivery and C2 domain â cdnorigin.net, *.trycloudflare.com
- [HTTP paths] Loader and controller API endpoints â /api/agent/full?arch=amd64, /api/agent/binary?arch=amd64, /api/register, /api/result/
- [HTTP headers] Agent authentication headers â X-Mesh-Auth, X-Operator-Key
- [File names / paths] Persistence and staging artifacts â /etc/cron.d/.sys-health, /etc/profile.d/sys_alias.sh, /tmp/.n4d_autodeploy_debug, /usr/local/bin/.sys-health-monitor
- [File names / paths] Temporary execution locations â /dev/shm/.n4d, /tmp/.agent, /var/tmp/.wd
- [SSH public key] Installed persistence key â AAAAC3NzaC1lZDI1NTE5AAAAIJKH4g/SD6c00i5PzlWWkwXJwIHEac+nlAjg6WeOHUq3
- [SHA-256] Retrieved or unpacked samples â fc4109f5dd1d30b65dd60e57dc639ac1d313bfa5241e36e61fbc4aabc1cda482, c422621ef824b627d74906f8d75ed8f990f4d6c708a0d263f219f9d9dd435174, and other hashes mentioned in the article
Read more: https://securitylabs.datadoghq.com/articles/n4d-mesh-controller-go-titan-new-infrastructure-hunting/