Suspicious outbound connection
An office device tried to reach an IP listed in the threat feed.
192.168.10.24203.0.113.42- Event time
- 10:42 · sample event
- Direction
- Outbound · from your network
- Why it matters
- Destination listed for malicious activity
- Action
- Connection blocked by feed policyConnection logged by feed policy
- Notification
- Local log; configured email or webhook
The matching connection is stopped, and the device is flagged for review. Blocking this connection does not establish that the device is clean.
This feed category logs the attempt and raises an outbound alert. It does not block the connection; other firewall rules still apply.
What makes this alert useful?
A clear alert identifies the source device, destination, feed match, event time and firewall action. Outbound events are grouped to reduce repeated notifications. Alerts go to the local system log by default; configure email or a webhook to reach your team.
The next step is to check the device and its endpoint security records. An IP match alone does not confirm ransomware.