This malicious IP was reported for trying to intercept VoIP calls, a type of eavesdropping attack aimed at capturing sensitive information.

This IP belongs to Wells Fargo.

It seems like this IP tried to spread malware into the network.

It attempted to send phishing emails from the Mail server.

The IP was involved in a rapid sequence of login attempts.

The IP has been tagged as a source for data mining spyware, aiming to gather personal information.

It was observed attempting to conduct a replay attack, resending captured SSH packets in hopes of session hijacking.

This particular IP displayed behaviour typical of a ransomware-infected system, encrypting several files.

This IP belongs to Oracle.

The IP tried to exploit buffer overflow vulnerabilities to run unauthorized code.

The IP sent malicious links via IM softwares, aiming to spread instant messaging worms.

Attempts to access the server using known malicious IP addresses or domains.

This IP belongs to Phillips 66.

It tried to execute a Rainbow Table attack, aiming to break the encryption used in SSH password protection.

The IP tried to launch 'Dark Tequila' malware that steals banking information and login credentials from the server.

The IP was seen trying to perform a FTP Reflection attack, using the FTP server to amplify its DDoS attack traffic.

This IP was seen trying to perform a SIP Torture attack, sending malformed SIP messages to crash or degrade the performance of the server.

It attempted to perform a Teardrop attack on the SSH server.

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 launched Spoofing attacks, trying to hide its identity by disguising itself as a trusted user or server.

It partook in whaling attacks, specifically targeting high-profile users within our system.

This IP belongs to Amazon Web Services.

POST /j_security_check: May indicate an attempt to bypass Java server page (JSP) login mechanisms.

The IP attempted to register with the VOIP server using an invalid username.

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