Select your language

WHAT ARE YOU LOOKING FOR?

Popular Tags

Raleigh, NC

32°F
Clear Sky Humidity: 45%
Wind: 1.63 M/S

Cyber-Threat

Hackers Exploit Hidden Cron Jobs to Reinstall Malware on Firewalls and Routers Every Five Minutes

Hackers Exploit Hidden Cron Jobs to Reinstall Malware on Firewalls and Routers Every Five Minutes

A newly uncovered Linux botnet is exploiting a persistence technique that hides in a place many network administrators rarely inspect: scheduled tasks running on routers, firewalls, switches, and other internet-connected infrastructure devices.

The malware, known as Evooo1Bot, maintains its foothold by secretly creating recurring cron jobs that automatically reinstall the malicious payload every five minutes. Even if defenders identify the malware process, terminate it, and delete its files, the botnet can rapidly restore itself by downloading a fresh copy from a remote server. Researchers at FortiGuard Labs first documented the threat on August 13, 2026, while a later analysis from Eclypsium highlighted how this persistence mechanism significantly complicates incident response efforts.

Unlike traditional endpoint malware that targets workstations and servers, Evooo1Bot primarily focuses on internet-facing network infrastructure, including routers, firewalls, IP cameras, network-attached storage (NAS) devices, VoIP phone systems, and other embedded Linux-based systems. Once installed, the malware leverages components derived from the leaked Mirai botnet source code, while introducing additional capabilities such as encrypted command-and-control communications, SSH password brute-forcing modules, and built-in proxy functionality.

Hidden Scheduled Tasks Enable Continuous Reinfection

At the core of Evooo1Bot’s persistence strategy is its abuse of cron, the standard task scheduler found on Linux systems. Cron is commonly used for legitimate administrative functions such as log rotation, maintenance scripts, health checks, and file cleanup. However, attackers have repurposed this trusted service as a stealthy persistence mechanism.

When attackers issue the malware’s !persist command, Evooo1Bot establishes several independent methods of surviving removal. One of the most effective is a cron task configured to execute every five minutes. The task silently uses utilities such as wget or curl to download a remote script and immediately execute it through a shell interpreter. As a result, even if security teams remove the malware binary and terminate all related processes, the next scheduled task execution restores the infection almost instantly.

The cron-based mechanism is only one layer of a broader persistence framework. Evooo1Bot also installs a systemd service deceptively labeled “Apache HTTPD Cache Manager,” creates traditional init scripts, modifies /etc/rc.local, and places startup scripts within /etc/profile.d/. These various persistence methods ensure that removing one component alone is insufficient to eradicate the infection.

Researchers further observed that the malware attempts to improve its survivability by reducing its likelihood of being terminated by the Linux Out-Of-Memory (OOM) killer. Additionally, it maintains active watchdog-related file handles that can help it survive circumstances that might otherwise interrupt malware execution.

Exploiting Known Vulnerabilities and Weak Credentials

The botnet does not rely on cron jobs for initial access. Instead, FortiGuard researchers report that Evooo1Bot spreads by exploiting publicly known vulnerabilities affecting devices from vendors including D-Link, Tenda, NETGEAR, Telesquare, and others. The malware also conducts SSH password-guessing attacks against exposed devices with weak or default credentials.

Analysis revealed that multiple exploitation chains ultimately contacted the same malware loader infrastructure. Once compromised, affected devices can be transformed into SOCKS proxy servers, enabling threat actors to conceal their true origins while conducting additional attacks. FortiGuard researchers identified this proxy capability as one of the botnet’s most dangerous features because it allows attackers to use trusted network appliances as pivot points for lateral movement within enterprise environments.

A Growing Trend in Botnet Persistence

Evooo1Bot is not the first malware family to adopt cron-based persistence. In February 2026, security researchers documented the SSHStalker botnet, which used a similar strategy by creating cron jobs that executed every minute to restart malware processes whenever they were removed.

Other campaigns have employed comparable watchdog techniques, with some malware restoring compromised systems within as little as 60 seconds after termination. These approaches demonstrate a growing trend among threat actors who seek to maintain long-term access through legitimate operating system functionality rather than more visible persistence mechanisms.

Why Infrastructure Devices Remain High-Value Targets

Network appliances often fall outside traditional security monitoring programs. Administrators typically manage these devices through vendor-specific interfaces and configuration tools, while underlying Linux operating system components receive far less scrutiny. Unlike corporate endpoints and servers, routers and firewalls frequently lack endpoint detection and response (EDR) agents, creating visibility gaps that sophisticated attackers actively exploit.

This blind spot has contributed to an increasing number of attacks targeting edge infrastructure, where malware can operate undetected for extended periods while providing adversaries with privileged access to network traffic and internal systems.

Detecting Hidden Cron Job Abuse

According to Eclypsium, incident responders should begin investigations by accessing the device’s underlying Linux shell whenever possible. On Arista EOS, administrators can enter a Bash environment directly, while Cisco NX-OS deployments may require the Bash shell feature to be explicitly enabled before inspection can occur.

Security teams should not declare a device clean simply because the Linux shell cannot be accessed. Instead, the inability to inspect scheduled tasks should be documented as a limitation during the investigation.

Responders are advised to review all scheduler-related locations manually, including:

  • /etc/crontab
  • /etc/cron.d/
  • /etc/cron.hourly/
  • /etc/cron.daily/
  • /etc/cron.weekly/
  • /etc/cron.monthly/
  • /var/spool/cron/
  • /var/spool/cron/crontabs/

Investigators should avoid relying solely on crontab -l, since an attacker operating with root privileges can write directly to spool directories without creating entries that would appear through standard administrative commands.

Particular attention should be given to jobs containing patterns such as:

  • curl or wget commands piped directly into sh or bash
  • References to /dev/tcp
  • Usage of nc or ncat
  • Long Base64-encoded strings
  • Tasks configured to execute every minute or immediately after reboot

While frequent scheduled jobs are not necessarily malicious because many vendors use them for legitimate maintenance operations, any task that downloads and executes remote code should be treated as a potential security incident.

Recommended Remediation Process

When removing Evooo1Bot or similar threats, responders should follow a deliberate sequence of actions. First, preserve forensic evidence by copying cron files and recording file timestamps. Next, remove malicious persistence mechanisms before terminating active malware processes. Failing to do so may allow the scheduler to immediately relaunch the malware during remediation.

After scheduled tasks have been removed, administrators should inspect additional persistence locations such as systemd services, init scripts, login scripts, and vendor-specific automation frameworks. Environments running Cisco NX-OS should also review Embedded Event Manager (EEM) applets, while Arista deployments should inspect event-handler configurations that may provide alternative persistence paths.

Although patching vulnerable devices remains critical for preventing initial compromise, security updates alone will not remove malicious cron jobs or persistence mechanisms already installed on affected systems. As demonstrated by recent infrastructure-focused threats such as the PEERSTITCH malware implant, attackers continue to capitalize on limited visibility within network appliances, making proactive inspection and continuous monitoring essential parts of modern defense strategies.

Found this article interesting? Follow us on X(Twitter) ,Threads and FaceBook to read more exclusive content we post. 

Cybersecurity Insight delivers timely updates on global cybersecurity developments, including recent system breaches, cyber-attacks, advancements in artificial intelligence (AI), and emerging technology innovations. Our goal is to keep viewers well-informed about the latest trends in technology and system security, and how these changes impact our lives and the broader ecosystem

Please fill the required field.