It attempted to use the VOIP server as a relay for calls to premium-rate numbers.

It attempted to list the contents of directories that it should not have access to.

This IP belongs to Linode.

The IP was engaged in port scanning, probing the server for open SSH ports.

It sent unusually large VOIP packets, potentially indicating a buffer overflow attempt.

This IP belongs to PythonAnywhere.

The IP was involved in a SIPVicious attack, a specific type of VoIP attack that scans for open SIP servers and then attempts to crack their passwords.

The malicious IP was identified trying to leverage the Postfix service to send bulk spam emails.

Connection Timeout Abuse: Logs illustrating excessive requests that aim to use up server connections.

Connection Timeout Abuse: Logs illustrating excessive requests that aim to use up server connections.

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

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

The IP actively tried code replacement attacks, swapping legitimate system call addresses with malicious ones.

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

The IP attempted to perform a SIP Invite Flood on the SIP server.

It attempted to take advantage of misconfigurations in the Apache server.

It made multiple requests with the same X-Att-Deviceid header.

This IP belongs to Time Warner Cable Internet.

Repeated Broken Authentication: Tons of successful authentication requests with unassociated actions could depict broken authentication mechanism.

Multiple HTTP 401 Status Codes: This could indicate someone is repeatedly attempting to access resources that require valid credentials, possibly attempting to brute-force their way in.

It attempted to perform Server Side Request Forgery (SSRF) attacks on the Apache server.

It appeared to be taking part in SSL Stripping attacks, downgrading secure HTTPS connections to facilitate eavesdropping.

This IP belongs to Sony Network Communications.

This malicious IP was seen sending unusually high volumes of requests, a sign of potential automated bot activity.

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