Port 162/udp: SNMP Trap
Category: Remote Management & Administration. Range: well-known. Status: iana registered.
What runs here
The reverse-direction channel from SNMP polling: instead of being queried, a managed device pushes an unsolicited notification (link down, temperature threshold, cold/warm start, and similar events) to a management station listening on port 162.
Why it matters
Because SNMPv1/v2c traps carry the same plaintext community string as regular SNMP queries, they are equally visible on the wire, and because a receiving station generally trusts whatever arrives on 162, forged or spoofed traps can be used to plant misleading status data in a monitoring system, or, in bulk, to flood and degrade the trap receiver itself.
Where you see it
Legitimately: network devices notifying a monitoring platform of state changes such as an interface going down or a device restarting. Anomalously/maliciously: spoofed or forged traps sent to mislead a monitoring system, or trap flooding as a minor denial-of-service against the receiver.
What to look for
| Signal | What it means |
|---|---|
| Traps from unmanaged sources | A trap arriving from a source IP with no corresponding managed-device entry in the NMS is inherently suspicious. |
Related ports
- 161/udp: SNMP (Simple Network Management Protocol)