The IP initiated dictionary attacks, hoping to guess the correct password combination.

This IP was reported for attempting a Dictionary attack on the VoIP server, systematically entering every word in a dictionary as a password to find the correct one.

This IP belongs to Jabil.

It attempted to use the POP3 server to relay phishing emails.

Multiple Sequential Page Requests: Quick, sequential requests to all pages of a site could be someone scanning for vulnerabilities.

This IP belongs to Airtel.

This malicious IP was reported for trying to inject malicious scripts into the VoIP server, potentially to disrupt its operation or steal data.

It seems like this IP tried to spread malware into the network.

It attempted to use the FTP server to distribute terrorist propaganda.

It attempted to exploit known vulnerabilities in the FTP protocol.

Multiple attempts to access the server using encrypted tunnels or proxies.

The IP attempted to perform a phishing attack using the SASL server.

Too Many HTTP 404 Errors: A high number of 404 Page Not Found errors may indicate an attacker trying to find valid directories or pages.

Identification of Known Vulnerabilities: Attempts to exploit known vulnerabilities related to your server application.

The IP attempted to perform a phishing attack using the SASL server.

This IP belongs to Intel.

The IP attempted to use the Mail server to relay emails with malicious links to other servers.

It was found that the IP had deployed rogue security software in our system.

Path Traversal / URI Encoding Attacks: You might notice HTTP GET requests that include ".." or "%2e%2e" or "%252e%252e", indicating a path traversal attack.

The IP was reported for attempting a Cross-Site Scripting attack, injecting malicious scripts into websites to steal data or disrupt functionality.

The IP was recorded making persistent attempts to crack our encryption.

The IP was involved in a traffic flooding attack, overwhelming a network's bandwidth to cause service disruption.

Multiple requests with identical request parameters.

The IP address initiated attacks using DDoS, impacting our server response times.

It launched a SYN flood attack, aiming to consume server resources and disrupt services.