Skip to content

KadNap Botnet Targeting ASUS Routers

alt text

KadNap Botnet ASUS Routers Proxy Abuse P2P C2

Overview

Researchers identified a malware campaign involving a botnet known as KadNap, which compromises ASUS routers and other edge devices and repurposes them as proxy nodes. These compromised devices are then used to relay malicious traffic, helping threat actors mask origin infrastructure during cybercrime operations.

Reporting indicates sustained growth since first observation in August 2025, with botnet access being leveraged in cybercriminal proxy-service ecosystems.

Technical Specifications

Attribute Details
Malware Family KadNap
Primary Targets ASUS routers and internet-exposed edge devices
Initial Stage Artifact aic.sh script downloaded from attacker infrastructure
Persistence Mechanism Cron job execution every 55 minutes
Main Payload ELF binary kad
C2/Coordination Method Modified Kademlia DHT (peer-to-peer control)
Operational Support NTP synchronization across infected nodes
Abuse Outcome Proxy network for anonymized malicious traffic

Affected Products

  • ASUS routers with vulnerable exposure/configuration states
  • Other edge devices susceptible to script/binary execution pathways
  • Networks with weak router credential hygiene or exposed management surfaces
  • Residential and SMB environments used as relay infrastructure
  • Status: Active botnet risk with global infection footprint

alt text

alt text

Technical Details

1) Initial Infection Script

  • Infection begins with retrieval of aic.sh from remote attacker-controlled servers.
  • Script orchestrates setup, payload download, and persistence logic.

2) Persistence

  • aic.sh creates a cron-based persistence task scheduled every 55 minutes.
  • Repeated execution supports malware durability and re-establishment after interruption.

3) Payload Deployment

  • Script retrieves and executes kad (ELF malware binary).
  • Device transitions into active KadNap bot/client behavior.

4) P2P Command Infrastructure

  • KadNap uses a modified Kademlia DHT model for bot discovery/coordination.
  • Decentralized peer architecture obscures direct C2 endpoints and complicates takedown.

5) Time Synchronization

  • Compromised devices contact multiple NTP servers to coordinate timing/operations.

6) Criminal Proxy Monetization

  • Infected nodes are reportedly integrated into proxy access offerings (e.g., Doppelganger-referenced reporting context).
  • Adversaries route malicious campaigns through hijacked residential/edge infrastructure.

alt text

Attack Scenario

  1. Reconnaissance:

    • Attacker scans internet for vulnerable ASUS routers/edge devices.
  2. Script Delivery:

    • Malicious aic.sh is fetched and executed on target device.
  3. Persistence Setup:

    • Cron job established to maintain recurring execution.
  4. Bot Payload Install:

    • kad ELF binary is downloaded and launched.
  5. Botnet Enrollment:

    • Device joins KadNap P2P botnet and synchronizes operations.
  6. Operational Abuse:

    • Device used as proxy relay for anonymized attacks and cybercrime activities.

Impact Assessment

  • Reported compromise of 14,000+ devices globally
  • Expansion of criminal proxy infrastructure using hijacked edge assets
  • Increased difficulty tracing true attacker origins
  • Residential/SMB networks exposed to abusive traffic relay
  • Potential interception or misuse of local network pathways
  • Elevated risk of follow-on exploitation from compromised gateway devices
  • Infrastructure for DDoS, credential stuffing, brute-force, and fraud operations
  • Enhanced operational cover for criminal campaigns via distributed proxies
  • Longer botnet survivability due to decentralized control model

Mitigation Strategies

Router and Edge Hardening

  • Update router firmware regularly from official vendor channels
  • Change default admin credentials and enforce strong unique passwords
  • Disable remote administration unless strictly required

Detection and Monitoring

  • Monitor router logs for suspicious outbound connections and recurring script activity
  • Track unusual cron entries, unknown binaries, and abnormal NTP/peer traffic patterns
  • Alert on signs of proxy-service abuse and unexplained network throughput spikes

Incident Response

  • Reset compromised routers to factory settings and securely reconfigure
  • Re-apply patched firmware and hardening baselines after reset
  • Block known malicious infrastructure and applicable indicators of compromise

Resources and References


Last Updated: March 11, 2026