This IP belongs to Ford Motor.

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

Remote File Inclusion (RFI): You might see HTTP requests with "=http" or "=ftp" which can signal an attempt for remote file inclusion.

The IP was seen trying to perform a Spoofing attack, falsifying its IP address to deceive the FTP server.

This IP belongs to Comcast.

The detected IP address was responsible for the distribution of botnets aimed at automating data theft.

This IP belongs to Humana.

POST /wp-admin/admin-ajax.php: The Actor may be trying to exploit some vulnerable WordPress theme or plugin.

The malicious IP was involved in a SPIT (Spam over IP Telephony) attack, sending unsolicited messages over the VoIP server.

It engaged in mail bombing, flooding the server with large amounts of insignificant mails.

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.

The malicious IP was involved in Smurf attacks, amplifying its denial-of-service attack using internet host IP network links.

This IP belongs to the University of California, Berkeley.

This IP was seen trying to perform a RTP Injection attack, inserting audio into an established VoIP call.

The IP was found to be behind numerous fileless malware attacks.

The IP tried to initiate DNS tunneling for smuggling data through SSH.

This IP was detected initiating zero-day exploit attacks on our system.

It attempted to use the FTP server to store illegal content.

The IP was seen attempting a FTP Command Injection attack, inserting malicious commands into legitimate FTP requests.

This IP belongs to Alphabet.

Conducted various IP scans, seeking loopholes in our network's security.

This IP belongs to United Technologies.

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

This IP belongs to CenturyLink.

It attempted to perform Insecure Direct Object References attacks on the Apache server.