It attempted to perform a credential stuffing attack on the SSH server.

The malicious IP was reported for engaging in port scanning, probing the server for open ports to discover potential vulnerabilities for exploitation.

This IP belongs to Cardinal Health.

Damaging activities showing connections to rootkit attacks were associated with this IP.

The IP attempted to perform a key exchange attack on the SSH server.

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

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

Participated in the notorious Water Torture attack to overload our DNS servers.

Our team discovered that specific IP was distributing intrusive cookie trackers.

The malicious IP was reported for sending a high volume of SIP INVITE requests, a potential sign of a call flooding attack.

The IP was caught attempting to execute heap overflow attacks.

The IP made repeated attempts to authenticate with the SIP server using different usernames.

The malicious IP was found to be running an Internet Relay Chat (IRC) bot, potentially spreading malware or launching Distributed Denial-of-Service (DDoS) attacks.

It made multiple requests with the same X-Forwarded-For header.

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

This IP was reported for attempting to register a large number of SIP extensions in a short time, a sign of a potential brute force attack.

The IP was seen trying to perform a Denial of Service (DoS) attack, attempting to make a machine or network resource unavailable to its intended users.

The IP sent malformed VOIP requests, potentially indicating an attempt to crash the server.

The IP attempted to send emails from the Mail server without proper authentication.

It attempted to send emails from the Postfix server to a large number of recipients.

This IP belongs to Berkshire Hathaway.

It attempted zero-day attacks, exploiting unknown vulnerabilities in pop3.

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

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

The malicious IP was reported for sending a high volume of SIP INVITE requests, a potential sign of a call flooding attack.