UDP traffic
Datagrams matching asn:51852 sent to HoneyLabs sensors over UDP in the last 7 days. DNS questions and QUIC client fingerprints are decoded on the sensor. Other datagrams are kept as their first bytes and labelled by protocol where it can be recognised.
A UDP source address can be forged, so each address listed here either sent the traffic or was impersonated by whoever did. UDP traffic is kept out of verdicts, feeds, watchlists and alerts.
Traffic by type
Other services
11 datagrams from 2 sourcesFirst packets of sessions with VPN, voice, tunnelling, database and management services.
Latest SIP datagram, to 5060/udp
INVITE sip:90113908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:28023;branch=z9hG4bK-524287-1---c21ef9fd43737445
From: <sip:x+13977481030@0.0.0.0>;tag=3133bd76
To: <sip:90113908351673002@<HONEYPOT>:5060>
Call-ID: sLRTlROFScojmA6fSCncy3..
CSeq: 15 INVITE
Contact: <si
payload bytes
Source addresses (unverified)
| Address | Network | Cc | Sends | Datagrams | Last seen (UTC) |
|---|
| 179.43.167.3 | AS51852 Private Layer INC | CH | SIP | 8 | 2026-10-06 16:56 |
| 179.43.134.194 | AS51852 Private Layer INC | CH | SIP | 3 | 2026-10-06 14:05 |
Latest datagrams
2026-10-06 16:56:19179.43.167.3to 5060/udpSIPCH INVITE sip:90113908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:28023;branch=z9hG4bK-524287-1---c21ef9fd43737445
From: <sip:x+13977481030@0.0.0.0>;tag=3133bd76
To: <sip:
payload bytes
2026-10-06 15:46:11179.43.167.3to 5060/udpSIPCH INVITE sip:90113908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:28023;branch=z9hG4bK-524287-1---02e862582da79026
From: <sip:x+13493984677@0.0.0.0>;tag=3ff17ba0
To: <sip:
payload bytes
2026-10-06 14:05:59179.43.134.194to 5090/udpSIPCH INVITE sip:694951898964@<HONEYPOT>:5090 SIP/2.0
Via: SIP/2.0/UDP 179.43.134.194:5745;rport=5745;branch=z9hG4bK0mmYcwLfdbgfk
Contact: <sip:460006170083@179.43.134.194:5745>
From: "460006170083"<sip:
payload bytes
2026-10-06 13:58:09179.43.167.3to 5060/udpSIPCH INVITE sip:0113908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:31620;branch=z9hG4bK-524287-1---999e219e64021c2f
From: <sip:x+16147230292@0.0.0.0>;tag=ac6a35ad
To: <sip:0
payload bytes
2026-10-06 07:33:40179.43.167.3to 5060/udpSIPCH INVITE sip:0113908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:31620;branch=z9hG4bK-524287-1---28c38fd9e6c4b21f
From: <sip:x+13493984677@0.0.0.0>;tag=4b3a893d
To: <sip:0
payload bytes
2026-10-06 05:45:03179.43.167.3to 5060/udpSIPCH INVITE sip:+3908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:31681;branch=z9hG4bK-524287-1---ae9b6b62c5fba465
From: <sip:x+16147230292@0.0.0.0>;tag=4224d476
To: <sip:+39
payload bytes
2026-10-06 04:32:12179.43.134.194to 5090/udpSIPCH INVITE sip:177507641111@<HONEYPOT>:5090 SIP/2.0
Via: SIP/2.0/UDP 179.43.134.194:6283;rport=6283;branch=z9hG4bK053v1x7S7y6n0
Contact: <sip:960014963145@179.43.134.194:6283>
From: "960014963145"<sip:
payload bytes
2026-10-06 03:06:03179.43.134.194to 5090/udpSIPCH INVITE sip:380158604494@<HONEYPOT>:5090 SIP/2.0
Via: SIP/2.0/UDP 179.43.134.194:9514;rport=9514;branch=z9hG4bK0D5Nr98GgoNGm
Contact: <sip:430000226962@179.43.134.194:9514>
From: "430000226962"<sip:
payload bytes
2026-10-06 00:28:08179.43.167.3to 5060/udpSIPCH INVITE sip:+3908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:31681;branch=z9hG4bK-524287-1---ba390fdaef5365a0
From: <sip:x+13977481030@0.0.0.0>;tag=31870793
To: <sip:+39
payload bytes
2026-10-05 23:16:42179.43.167.3to 5060/udpSIPCH INVITE sip:+3908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 0.0.0.0:31681;branch=z9hG4bK-524287-1---67ab4c0b973d8a16
From: <sip:x+13493984677@0.0.0.0>;tag=2fb72281
To: <sip:+39
payload bytes
2026-10-05 20:37:50179.43.167.3to 5060/udpSIPCH INVITE sip:8103908351673002@<HONEYPOT>:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 179.43.167.3:22545;branch=z9hG4bK-524287-1---5880356d83c0a82b;rport
Remote-Party-ID: <sip:16493984677@<HONEYPOT>>;p
payload bytes