The IP initiated a 'Deauth' attack, knocking legitimate users off the Apache service.

This IP belongs to Phillips 66.

The IP was involved in a RTP Bleeding attack, exploiting vulnerabilities in the VoIP server to listen to ongoing calls.

It made multiple requests with the same Max-Forwards header.

It showed unusual patterns in the sequence of requests.

This IP belongs to IBM.

Various incidents of unwanted installation of malicious gaming apps were traced back to this IP.

The IP attempted to exploit known vulnerabilities in the VOIP protocol.

This IP belongs to AT&T.

This IP belongs to Comcast.

It performed botnet operations, controlling a group of “zombie” computers to amplify its DDoS attacks.

Multiple requests with the same Origin header.

The malicious IP attempted to gain unauthorized access to the server by repeatedly trying different username and password combinations.

This malicious IP attempted a brute force attack, trying to crack login credentials to gain unauthorized access to a system or account.

It launched SQL injection attempts, to break our server database through poorly secured entry fields.

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

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

This IP belongs to Bristol-Myers Squibb.

Repeated Unique 404 Errors: Logs revealing a steady stream of unique 404 errors could suggest a DDoS attack aiming to exhaust storage resources.

It made multiple requests with identical Accept-Charset headers.

It was identified as a BadBot, a type of bot that performs malicious activities.

The malicious IP initiated numerous HTTP flood attacks, designed to overwhelm the Apache server with requests.

The IP tried to crack S/MIME encryption for accessing secured email contents.

The malicious IP was reported for trying to perform a VoIP Phreaking attack, exploiting weaknesses in VoIP systems to make free calls or disrupt services.

Frequent password reset requests.