Today is one of those Whiskey Tango Foxtrot kind of days. I've been tracking a real November Sierra since December, and even reported it. I figured it was a bug, so I submitted it to the security folks. Their response? "We're not the team for this problem." ok. Now today I see two data points, one weird-o one-timer kind of probe. Yup, for real, a solo IP in the gigabytes of logs that my splunk eats. Yet this IP correlates with another IP that has been on my radar. So I get out my splunk and pull a "deny" query on this IP. Not only does it generate IPS hits from my desktop, outbound to destination, but I see inbound activity from this IP (also denied, of course). ( 2017 - 03 - 29T17 : 56 : 44 ) firewall : msg _ id = " 3000 - 0150 " Deny 1 - Trusted 0 - External 9840 tcp 20 64 [desktop_ip] 184 . 86 . 92 . 71 12766 80 offset 5 A 2936268642 win 342 signature _ name = " WEB - CLIENT WScript . Shell Remote Code Execution...