This IP belongs to Amazon Web Services.

Several instances of password stealers were traced back to this notorious IP.

It attempted to use the FTP server to distribute traffic monitoring tools.

This IP belongs to Boeing.

It attempted to login to the FTP server with an invalid password.

Multiple 5xx Server Error Codes: A high count of server error status codes such as '500 Internal Server Error' may suggest an attacker is probing the server's security.

The notorious IP attempted to distribute Banker Trojans aimed to steal financial data.

This IP belongs to Cigna.

The IP attempted several directory traversal attacks, aiming to access files beyond the root directory.

The IP tried to carry out illegal 'HTTP Request Smuggling' to fool the Apache server.

The malicious IP was involved in a credential stuffing attack, using stolen username-password combinations to gain unauthorized access.

It attempted to delete emails from the POP3 server without authorization.

Unusually high number of requests to the login page.

The malicious IP was reported for attempting a Session Teardown attack, sending BYE messages to end SIP sessions prematurely.

This IP belongs to Prudential Financial.

The IP was seen trying to perform a PASV FTP Bounce attack, misusing the passive mode to scan other hosts and ports.

It attempted to perform a SIP Invite Flood on the VOIP server.

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

This IP belongs to Morgan Stanley.

It attempted to use the Postfix server to relay malware-infected attachments to other servers.

It attempted to send phishing emails from the Mail server.

It actively attempted to employ session-splicing techniques, interacting with multiple SSH sessions simultaneously to smudge its attack trace.

This IP belongs to IBM.

The IP was caught distributing VoIP crackers to exploit our communication channels.

It attempted to perform a SIP Register Flood on the Asterisk server.