Scan.generic.portscan.udp Kaspersky Apr 2026

Maya, the night shift SOC analyst, frowned. A UDP port scan from a marketing laptop at three in the morning was either a misconfigured backup script or something far worse. She pulled up the logs.

Kaspersky had caught it not as an exploit, but as a behavior – the generic signature of something feeling its way through the dark.

Maya killed the laptop’s network port. Then she called Derek. “Congratulations on the baby. Now, about your computer…” scan.generic.portscan.udp kaspersky

She ran a memory dump. The laptop’s RAM contained a tiny, nameless process – a binary that had arrived via a phishing PDF three days ago, undetected until now. The PDF was an invoice. Derek, sleep-deprived with a newborn, had clicked it at 2 AM.

The alert blinked on Kaspersky’s central console: – source: workstation 14-B, time: 03:14 AM. Maya, the night shift SOC analyst, frowned

He never even knew his machine had been whispering to the void. But the void had almost whispered back.

The laptop’s owner, Derek from creative, was supposedly on paternity leave. His machine, however, was alive with chatter – a staccato burst of empty UDP packets hammering against the finance department’s VPN gateway. Not a targeted attack. Generic. Noisy. Amateur. Kaspersky had caught it not as an exploit,

“Probably a worm,” she muttered, isolating the device. But Kaspersky’s behavioral engine flagged something else: the scan wasn’t random. It was probing port 161 (SNMP) and port 137 (NetBIOS) in a slow, rhythmic pattern. Not a scan for vulnerabilities. A scan for echoes .

Inside the process, she found the twist: the UDP scanner wasn’t trying to break in anywhere. It was listening. Every UDP packet it sent was crafted with a unique identifier. When a misconfigured server replied with an ICMP “port unreachable,” the malware noted the response time. It was mapping the shape of the network’s silence – building a low-frequency covert channel to exfiltrate data one bit per dropped packet.