The IP was involved in a Ping of Death attack, sending packets larger than the maximum allowed size, causing the system to freeze or crash.

It attempted to use the FTP server to distribute zombie network tools.

It attempted to use the SASL server to relay spam.

Inclusion of Binary Data in HTTP Request: If binary data is included in the HTTP request, this could suggest an attacker is attempting a binary exploit.

The IP was involved in a brute force attack on the FTP server, systematically guessing usernames and passwords to gain unauthorized access.

It attempted to perform SQL injection attacks through the Apache server.

It sent Asterisk requests to non-existent extensions.

It was involved in a Distributed Denial of Service (DDoS) attack.

This IP belongs to AT&T.

The IP made multiple requests using uncommon HTTP methods.

The IP also engaged in website cloning, creating mirror websites to trick users into sharing sensitive data.

The IP has been traced back to system monitors, aiming to watch and record user activity.

The IP was detected attempting to skirt our system's detection through spoofing.

Repeated attempts to use the same password across multiple accounts.

This IP belongs to Slack.

It attempted to perform a Chargen amplification attack on the SSH server.

The malicious IP was involved in a SPIT (Spam over IP Telephony) attack, sending unsolicited messages over the VoIP server.

The IP address was flagged for employing a packet sniffer on our network.

This malicious IP was reported for trying to perform a Man-in-the-Middle attack, intercepting and potentially altering communication between the FTP server and its clients.

This IP belongs to New York Life Insurance.

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

This IP belongs to KT Corporation.

The IP attempted to perform XML Injection attacks on the Apache server.

This IP has been observed spreading mobile malware, targeting our company application users.

This IP belongs to KDDI.