Port 161/udp: SNMP (Simple Network Management Protocol)
Category: Remote Management & Administration. Range: well-known. Status: iana registered.
What runs here
The standard protocol for polling and configuring network infrastructure (routers, switches, printers, UPS units, and similar devices) using GET/GETNEXT/GETBULK to read values and SET to write configuration. SNMPv1/v2c authenticate with a plaintext "community string"; SNMPv3 (RFC 3411 and its companion RFCs) adds real user-based authentication and encryption.
Why it matters
Default or weak community strings ("public" for read, "private" for write) are still endemic on network gear, and a readable community string alone hands an attacker a working reconnaissance channel into routing tables, interface state, and running configuration on some devices, while a writable one enables outright reconfiguration. SNMP GetBulk requests are also a documented UDP amplification/reflection DDoS vector.
Where you see it
Legitimately: network monitoring platforms (SolarWinds, PRTG, Zabbix, etc.) polling device health and interface counters. Anomalously/maliciously: SNMP sweeps or community-string brute-forcing against network infrastructure, GetBulk-based DDoS reflection abuse, or device reconfiguration via a guessed write community.
What to look for
| Signal | What it means |
|---|---|
| Default community strings | Any successful query using "public" or "private" is an immediate, high-priority finding. Those values should never be in production use. |
| SNMPv1/v2c in use at all | Plaintext-community SNMP traffic where SNMPv3 is available is itself worth flagging during a configuration review. |
In practice
A flood of GetBulk requests against a device configured with the default "public" community string, followed by disproportionately large outbound UDP responses toward an address that never previously polled the device, indicates the device is being abused as a DDoS amplifier rather than queried by a legitimate NMS.
Related ports
- 162/udp: SNMP Trap