We noticed the IP attempting to compromise our IoT devices by spreading IoT malware.

This IP was accused of multiple unauthorized removal of security certificates.

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.

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

The IP engaged in a mail relay attack, using our server to send spam.

It systematically tried to exploit IMAP and POP3 vulnerabilities present in our mail service setup.

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

This IP belongs to Deutsche Telekom AG.

Repeated requests for the same file or page, indicating an attempt to crack a password or exploit a vulnerability.

It partook in location spoofing, making it appear from different locations.

Bogus pop-ups irritating our end-users were found to be released by this infamous IP.

Repeated attempts to use the same password across multiple accounts.

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

This IP belongs to Mondelez International.

This IP belongs to Medium.

It was detected trying to perform cross-site scripting to bypass the same origin policy on Apache.

Participated in a botnet attack to overwhelm our server’s resources.

This IP belongs to Dropbox.

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

The malicious IP was reported for attempting a SIP Ping attack, sending SIP OPTIONS messages to discover SIP servers or users.

This IP was associated with targeted spear phishing attempts against our senior staff.

The IP made multiple unsuccessful login attempts in a short period of time.

This IP belongs to FedEx.

Automated Bot Traffic: Logs are showing an unusual large amount of traffic from known or suspected bot IPs.

It attempted to use the SSH server as a proxy for other malicious activities.