Skip to main content
Legia

Cybersecurity

Office Devices Turned Into a Botnet: Signs, Impact, and Response Steps

Routers, CCTV cameras, or NAS devices taken over by a botnet rarely look broken. The signs are in network traffic and in the reputation of the office IP address. Here is how to recognize, check, and handle them.

SEO and Content Specialist

7 min read Reviewed by Legia Cybersecurity Team

A glowing laptop keyboard in a dark room

Short answer: office devices infected by a botnet usually keep working as normal, so the signs are found on the network: high outbound traffic during quiet hours, repeated connections to unfamiliar addresses, devices sending email even though they are not mail servers, or the office IP address landing on a blocklist. Handle it by isolating the device, recording its traces, reinstalling the firmware, changing default passwords, and then checking other assets that share the same weakness.

News that office devices are infected by a botnet rarely comes from users. What happens more often: the internet provider sends an abuse notice, company email starts being rejected by recipients, or the office internet slows down for no clear reason. A botnet is a collection of devices that have been taken over and are controlled remotely, and the devices most often hit are the ones that get the least attention: routers, firewalls, NAS units, CCTV cameras, and other IoT devices. This article is for IT teams and management who need to decide on next steps: which signs to look for, what to check, how to handle it, and when a broader security assessment is needed.

Why do office devices become botnet targets?

Office devices become targets because they are connected to the internet all the time, rarely updated, and rarely monitored. In September 2024, the FBI, the Cyber National Mission Force, and the NSA issued a joint advisory about a botnet that, as of June 2024, consisted of more than 260,000 devices: small office and home office (SOHO) routers, firewalls, NAS units, and IoT devices, spread across the Americas, Europe, Africa, Southeast Asia, and Australia.

Two points in that advisory matter to decision-makers. First, the compromised devices were used as intermediaries to conceal the actors’ identities while launching DDoS attacks or breaking into target networks. In other words, your device is not the final target, but the attack is recorded as coming from your company’s IP address. Second, many of the infected devices were likely still supported by their vendors. Firmware updates alone are not enough if features such as UPnP, remote management, and file sharing are left switched on without a need, because those are the features abused to get in and to spread to other devices.

Illustration: cybersecurity

Signs that office devices are infected by a botnet

The signs that office devices are infected by a botnet almost always show up on the network, not on the device’s own screen. The table below summarizes the most common signs and where to check them.

SignWhere to checkWhy it is suspicious
High outbound traffic, including outside working hoursRouter or firewall bandwidth graphsThe device is sending data or taking part in a DDoS attack
Repeated connections to unknown IP addresses or domainsFirewall logs and DNS logsThe device is contacting a control server
A device that is not a mail server opening outbound connections to port 25Firewall logsA trait of devices used to send spam
The office public IP address is on a blocklist, office email is rejectedIP reputation checker, email rejection messagesLists such as the Spamhaus XBL contain the IPs of devices hijacked by malware
Abuse notices from the internet provider or an outside partyTechnical contact mailboxOthers see attacks coming from your IP
New admin accounts, changed port forwarding or DNS, devices restarting on their ownDevice admin panelThe configuration has been changed by someone else

A single sign does not necessarily mean an infection. A traffic spike can come from a cloud backup, and a restart can be caused by a power cut. What deserves follow-up is a sign that cannot be explained by a known schedule or activity. Rejected email can also be caused by incomplete domain records rather than an infection. Check both, for example with the guide to SPF, DKIM, and DMARC for company email.

The impact on the company

A device that has become part of a botnet harms the company even when no data is stolen:

  • IP address reputation. While the office IP is on a blocklist, company email can be rejected or land in spam. Spamhaus states that an IP removed from its list will be listed again if the underlying problem has not been fixed.
  • Bandwidth and services. The office connection slows down, and services sharing the same line are disrupted too.
  • A way into the internal network. A compromised device sits inside the office network and can be used to spread malware to other devices.
  • Attacks in the company’s name. Attack traffic is recorded as coming from your IP address, so it is the company that has to explain it to the internet provider or to the party being attacked.

What does the IT team check?

The check starts with a list of devices, then traces how they behave on the network. A practical order:

  1. An inventory of connected devices, including the ones often overlooked: CCTV cameras, video recorders (NVR or DVR), network printers, NAS units, wireless access points, and devices installed by vendors.
  2. Firewall and router logs: the most frequent outbound destinations per device, when they occur, and their volume.
  3. DNS logs: the domains each device looks up. Devices with a narrow job, such as cameras or printers, should only contact a few destinations.
  4. Open services: UPnP, remote management, file sharing, and port forwarding rules whose purpose nobody knows.
  5. Passwords: whether default passwords have been changed. Many IoT devices have a separate administration password alongside the user accounts, and this one is often forgotten.
  6. Firmware versions and vendor support status: devices past their end of support (end-of-life) no longer receive patches.

Response steps when a device is confirmed infected

Handling a botnet in the office follows the order of isolate, record, clean, and then close the way in:

  1. Isolate. Disconnect the device from the network or move it to a separate segment. For computers, do not switch them off right away; the principle is the same as the first steps when an office is hit by ransomware.
  2. Record before cleaning. Save the time of discovery, the destination addresses of connections, log excerpts, and the device configuration. These notes are the material for finding the entry point.
  3. Block suspicious destinations on the firewall, and limit outbound connections to port 25 to the mail server only.
  4. Clean the device. Reinstall the firmware from the vendor’s website, restore factory settings if needed, then set it up again with a new password. A restart stops all running processes and can remove malware that lives only in memory, but it also wipes its traces, so do it after step 2. Malware stored on the device does not disappear with a restart alone.
  5. Close the way in. Switch off UPnP, remote management, and file sharing that are not in use, then replace end-of-life devices with devices still supported by the vendor.
  6. Separate the network. Place IoT devices in their own segment with just enough access for their function. Firewalls and separated networks are part of the Office Network Installation work.
  7. Monitor again and restore reputation. Once traffic is back to normal, request removal from the blocklist through the list provider’s reputation checker.

To build a standing procedure, NIST SP 800-61 Rev. 3 (April 2025) contains incident response recommendations linked to the NIST CSF 2.0 framework, so the steps above can become part of the company’s incident response plan.

When is a broader security assessment needed?

A broader security assessment should be done once the situation is under control, because one infected device often signals that the same weakness exists elsewhere. Consider an assessment if:

  1. The entry point was not found, so it is unclear whether the gap has been closed.
  2. More than one device was infected, a sign that the same configuration or password pattern is used in many places.
  3. Internet-facing assets were also affected, such as servers or applications reachable from outside.
  4. Systems change often, so new flaws can appear every month.

Legia’s Vulnerability Assessment maps flaws in websites, applications, servers, and the cloud without exploiting them, then organizes them into a prioritized report based on CVSS along with remediation steps. The whole process usually takes 2 to 4 weeks, retesting after fixes is included, and the check can be repeated every month for assets that change often. If what you need is proof of how far a single flaw can be exploited, read the difference between vulnerability assessment and penetration testing.

Note that Legia provides project-based security testing and regular checks, not 24-hour monitoring or on-call incident response. Isolation and cleanup during an ongoing incident are still done by your IT team; Legia’s assessment comes afterward, to make sure similar flaws do not remain in other assets.

Frequently asked questions

Is antivirus enough to detect a botnet in the office?

Not for every device. Antivirus runs on computers, while routers, cameras, and NAS units generally cannot have antivirus installed. That is why firewall logs, DNS logs, and traffic graphs are the main source for spotting infected devices.

Is it enough to restart a suspected device?

No. A restart can remove malware that runs only in memory, but malware stored on the device remains, and the gap used to get in is still open. The device needs its firmware reinstalled, its passwords changed, and unused services shut off.

Does an infected device have to be replaced?

Not always. A device still supported by its vendor can be cleaned and reconfigured. A device past its support period should be replaced, because its new flaws will never be patched.

How do we stop it from happening again?

Change all default passwords, switch off unused services, update firmware regularly, separate IoT devices into their own segment, monitor outbound traffic, and schedule regular security checks for internet-connected assets.

Sources

Details on the scope and process of the assessment are on the Vulnerability Assessment page, or see all of Legia’s Cybersecurity services.

Category Cybersecurity

Keep reading

Related articles

All Articles