The IP attempted to manipulate data flowing to the server to cause arbitrary code execution.

The IP attempted to use the FTP server to distribute forensics tools.

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.

POST /user/password?name[0,%20bypass]=dav&name[0]=loup&pass-reset-token-1=D&form_id=user_pass: Drupalgeddon2 exploit which allows remote code execution.

This IP belongs to FedEx.

It attempted to exploit known vulnerabilities in the Postfix software.

This IP belongs to Abbott Laboratories.

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

This IP belongs to Wells Fargo.

It initiated SSL-Stripping attacks, aiming to downgrade secure HTTPS connections to less-secure HTTP.

This IP belongs to Facebook.

This IP belongs to PythonAnywhere.

It tried to execute Privilege Escalation attacks, trying to gain higher-level access on our server.

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

Login attempts using old or outdated protocols.

The suspicious IP attempted to introduce spyware under the guise of software updates.

Incriminating activities involving the distribution of trojan horses were linked to this IP address.

Participated in a botnet attack to overwhelm our server’s resources.

The IP was traced back to stealthy installation attempts of clipboard monitors.

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

This IP belongs to PepsiCo.

The IP attempted to use the FTP server to distribute keylogging software.

This IP belongs to Massachusetts Mutual Life Insurance.

Ping of Death: Logs showing oversized ICMP requests could suggest Ping of Death attacks.

This IP belongs to Cloudfare.