Back to Newsroom

Threat intel6 min read

Evooo1Bot hides in firewall cron jobs and reinstalls itself every five minutes

A Mirai-based Linux botnet exploits 18 known flaws in routers, firewalls, cameras and NAS boxes, turns them into proxies and uses a five-minute cron job to come back after cleanup. Here is how to check your devices.

4Tify Team

A Linux botnet called Evooo1Bot is turning routers, firewalls and other edge devices into proxies for its operators, and it is built to survive the usual cleanup. When it is told to persist, it writes a cron job that downloads and runs the malware again every five minutes. Kill the process, delete the file, and the device can be reinfected before the incident ticket is closed.

What happened

Evooo1Bot was first documented publicly on 13 August 2026. It had been attacking internet-facing devices since July. The name comes from the string "evooo1", which is hardcoded into every sample. The DDoS part of the bot is lifted from Mirai, whose code leaked in 2016, but the operators added a lot on top: encrypted command-and-control traffic over port 443, an SSH password-guessing scanner with a list of more than 150 credentials, a sniffer for HTTP login headers and cookies, and a module that turns the infected device into a SOCKS5 proxy.

That proxy feature is the one a company should worry about most. An attacker can route traffic through your router or firewall, hide their real origin behind your IP address, and use the device as a foothold to reach the internal network.

On 17 November, a detailed defender guide focused on the part most teams miss: the scheduled jobs that run underneath the vendor's management interface.

Who is affected

The bot goes after exposed routers, firewalls, IP cameras, PBX phone systems and NAS boxes. In observed attacks it exploited known flaws in devices from Alcatel, D-Link, Mitsubishi Electric, NETGEAR, Tenda and Telesquare. Its built-in exploit module carries eight more, including bugs in Hikvision cameras, Zyxel firewalls, the TP-Link Archer AX21, PHP-CGI and Atlassian Confluence. That makes 18 known vulnerabilities in total, the oldest from 2007.

Eleven of the 18 are already in the CISA Known Exploited Vulnerabilities catalog, among them the D-Link router flaw CVE-2022-37055. None of this is new. The bot does well because old, unpatched devices stay online for years. Devices with weak SSH passwords are at risk even when their firmware is current.

No one has published a count of infected devices, and the botnet has not been tied to a known group.

How the persistence works

A single bot command, !persist, installs five footholds at once:

  • a cron entry that runs every five minutes and pipes a script from wget or curl straight into a shell;
  • a systemd service with the harmless-looking description "Apache HTTPD Cache Manager", set to restart always;
  • an init script under /etc/init.d/;
  • a line in /etc/rc.local;
  • a login script under /etc/profile.d/.

The malware also lowers its priority for the out-of-memory killer and holds /dev/watchdog open, which makes it less likely that a hardware watchdog reboot will interrupt it. Removing only the cron line leaves the other four in place.

Many firewalls and switches run Linux underneath (Arista EOS, Cisco NX-OS and F5 BIG-IP among them), and cron comes with it. Admins work in the vendor CLI, configuration tools track the vendor settings, and endpoint agents rarely run on these boxes. So nobody looks at the crontab.

What to do now

  1. Patch or retire exposed devices. Check your edge hardware against the 18 CVEs and the KEV catalog. Replace devices that no longer get firmware updates, and change default or weak SSH passwords. CISA keeps its edge device guidance in one place.
  2. Open the Linux shell, not just the vendor CLI. On Arista EOS, bash from privileged mode gives you one. On Cisco NX-OS it needs feature bash-shell, which is off on many deployments. If you can't get a shell, write down that cron was not checked. Don't mark the device clean.
  3. Read the scheduler files directly. Look at /etc/crontab, /etc/cron.d/, the hourly, daily, weekly and monthly folders, and the spool under /var/spool/cron/ and /var/spool/cron/crontabs/. crontab -l is not enough, because an attacker with root can write to the spool directly.
  4. Search for the warning signs. curl or wget piped into sh or bash matches this botnet. /dev/tcp, nc or ncat points to a reverse shell, and a long base64 string usually hides a command. Jobs that run every minute or at @reboot deserve a look, though some vendors run legitimate frequent jobs.
  5. Clean up in the right order. Copy the cron file and its timestamps, remove the entry, and only then kill the process. Then check systemd units, init scripts, rc.local, /etc/profile.d/ and the vendor's own schedulers (NX-OS scheduler and EEM applets, Arista event handlers).
  6. Treat any download-and-run job as a breach. It means someone had root on the device. Hand it to incident response. Patching closes the way in but does not delete a job that is already there.

Botnets like this one live on devices their owners have forgotten about. Our Attack Surface Management service maps the routers, firewalls, cameras and other hardware you have facing the internet, flags the ones running firmware with known exploited flaws, and keeps watching as new devices appear.

NEWSLETTER

The week’s news,
every Friday.

A short email with what we published that week. You can unsubscribe from any of them.

FRIDAY DIGEST · SAMPLE4TIFY NEWSROOM

This week in security

  • 01Attackers exploit critical Cisco Expressway flaw to gain root on clustered nodes
  • 02SonicWall ends Gen 6 firewall patches, even for critical flaws
  • 03WhatsApp fixes three flaws, one possibly used to back up scam messages

+ 6 MORE IN THIS ISSUE · UNSUBSCRIBE IN ONE CLICK

ONE OFFER

More than one product?
Get one offer.

Tell us what you need to protect and your budget, monthly or yearly. We combine the products into one offer and one contract, sized to that budget, and we stay with you after it is signed.

Ask for an offer Just tell us how many assets you have and what you want to spend.
Evooo1Bot botnet: cron persistence on routers and firewalls | 4Tify