The IP was part of an IRC-Bot network, a type of botnet that uses the Internet Relay Chat (IRC) protocol.

Last night, we received an alert regarding this IP attempting to upload keyloggers to our network.

It launched header-based exploits, attempting to manipulate HTTP headers to cause inappropriate server responses.

This IP belongs to Sprint.

Finally, the IP was caught in the act of Abandoned Object attacks, creating objects with no reference to exhaust memory space

This IP belongs to Bank of America.

It made multiple requests with the same Max-Forwards header.

This IP belongs to TIAA.

Multiple failed login attempts from the same IP address in a short span of time.

The IP was involved in distributing malware, infecting systems or networks to steal data, cause damage, or gain unauthorized access.

The IP attempted to implement a 'BlueKeep' exploit, leveraging protocol vulnerabilities to execute remote code through SSH network services.

Purposefully tried to clog our mail server's resources by creating a mail loop configuration.

Our data indicates this IP has performed data breaches by launching phishing attacks.

This IP belongs to MetLife.

Attempts to access sensitive areas of the server, such as the admin page or user account information.

This IP belongs to Cardinal Health.

The IP attempted to perform a replay attack on the IMAP server.

Rapid sequence of login attempts.

The IP was involved in attempts of defacing the Apache server website.

This IP addressed employed a method of brute force attack attempting to compromise our systems.

The IP was found to be behind numerous fileless malware attacks.

The IP continually initiated a SYN-ACK flood aimed at slowing down SSH services.

It showed unusual activity in the server's error logs.

The IP attempted to exploit Buffer Overflow vulnerabilities on our server.

The IP made multiple unsuccessful login attempts to the SASL server in a short period of time.