Microsocks
- Type
- Proxyware
- Capabilities
- Lateral movementPost exploitationDefense evasion
- Platforms
- LinuxNetwork deviceIOT
MicroSocks is an open-source SOCKS5 proxy server used legitimately for network proxying and abused by threat actors for tunneling, pivoting, and concealing malicious traffic. It is a dual-use utility rather than an inherently malicious implant. Attackers deploy it on compromised Linux hosts, routers, and security appliances to reach internal services or enroll devices into proxy infrastructure. Observed deployments include Ubiquiti EdgeRouters, SonicWall Secure Mobile Access appliances, FortiWeb firewalls, and TP-Link consumer routers.
In an intrusion culminating in Abyss ransomware, attackers used MicroSocks on a compromised SonicWall appliance to tunnel RDP traffic into the internal network, reducing the need for additional internal backdoors. Other deployments have supported residential proxy networks and covert access through telecommunications infrastructure. Adapted builds have used predefined listening settings and username-and-password authentication. Router deployment scripts have distributed architecture-specific binaries, disguised running processes, and established persistence through external startup mechanisms; these surrounding mechanisms are not intrinsic MicroSocks capabilities.
MicroSocks has appeared in criminal infrastructure also accessed by Pawn Storm, in Head Mare operations targeting Russian organizations, and in the telecommunications-focused toolkit of CL-STA-0969, which overlaps with Liminal Panda. Its availability and use across unrelated operations mean its presence alone does not establish threat-actor attribution.
Associated vulnerabilities
1 CVE Mallory has correlated with this family across public research and vendor advisories. Each card links to the full Mallory page for that vulnerability.
Associated threat actors
3 distinct threat actors Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.
In some cases, the actor used a slightly different adapted version of MicroSocks with both the listening address (all interfaces) and port (56981/tcp) predefined.
Также в рамках атак мы зафиксировали инструмент MicroSocks — реализацию SOCKS5-прокси, полученную из открытого репозитория на GitHub.
...using a mix of custom and public tools such as Microsocks, FRP, FScan, and Responder...
Techniques & procedures
17 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
1 technique
Initial Access
The primary payload, tplink_stager.sh, was designed for post-exploitation of CVE-2024-21833, an OS command injection vulnerability affecting TP-Link Archer and Deco series routers.
Execution
2 techniques
Execution
Persistence on the TP-Link devices was achieved through three mechanisms: Cron -> /var/spool/cron/crontabs/root or /etc/crontabs (every 5 minutes).
All payloads are POSIX shell scripts; command execution via eval.
Persistence
3 techniques
Persistence
Persistence on the TP-Link devices was achieved through three mechanisms... RC scripts -> modification of /etc/rc.local.
Persistence on the TP-Link devices was achieved through three mechanisms: Cron -> /var/spool/cron/crontabs/root or /etc/crontabs (every 5 minutes).
Persistence on the TP-Link devices was achieved through three mechanisms... NVRAM -> writing to rc_startup via nvram set / nvram commit.
Privilege Escalation
2 techniques
Privilege Escalation
Persistence on the TP-Link devices was achieved through three mechanisms... RC scripts -> modification of /etc/rc.local.
Persistence on the TP-Link devices was achieved through three mechanisms: Cron -> /var/spool/cron/crontabs/root or /etc/crontabs (every 5 minutes).
Stealth
4 techniques
Stealth
Using exec -a '[kworker/0:1]', the proxy binary masquerades as a kernel worker thread while starting a SOCKS5 listener.
tplink_stager.sh self-deletes original and cleans wget/curl temp files.
Persistence on the TP-Link devices was achieved through three mechanisms... NVRAM -> writing to rc_startup via nvram set / nvram commit.
Dot-prefixed filenames on routers (/tmp/.m, /tmp/.s, /tmp/.bp, /tmp/.bid).
Discovery
2 techniques
Discovery
The device’s public WAN IP is retrieved via ipinfo.io or ifconfig.me.
All payloads collect hostname, username, and architecture via uname -m.
Lateral Movement
2 techniques
Lateral Movement
In our investigation, the attacker tunneled RDP traffic into the internal network through the compromised SonicWall.
In our investigation, the attacker tunneled RDP traffic into the internal network through the compromised SonicWall.
Command and Control
5 techniques
Command and Control
Deze software creëert een socks5 proxy wat vermoedelijk gebruikt wordt door actoren om malicieuze activiteiten te ontplooien.
T1090.001 Proxy: Internal Proxy PhantomCore использовали механизм проксирования трафика для организации связи между скомпрометированными узлами Rsocx, tsocks, wstunnel, microsocks, localtonet
Также в рамках атак мы зафиксировали инструмент MicroSocks — реализацию SOCKS5-прокси, полученную из открытого репозитория на GitHub.
Jesta researchers studied the activity and determined that the agent's apparent objective was proxyjacking by compromising weakly secured servers and deploying MicroSocks SOCKS5 proxies to create a distributed network of relay infrastructure.
Downloading microsocks binaries, GOST, FRP, and scanner modules from C2.
Observables
3 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.