The IP attempted reconnaissance activities, trying to footprint our server’s network.

This IP was suspected of running a botnet, a network of compromised computers used for malicious activities like spamming or DDoS attacks.

It launched invasive malware to corrupt crucial segments of our server functionality.

GET /ELMAH.axd: Attempting to exploit ELMAH (Error Logging Modules and Handlers) misconfiguration in ASP.NET sites.

This IP belongs to Fannie Mae.

It participated in Unvalidated Redirects and Forwards attacks, leading users to malicious websites via altered SSH links.

It attempted to send emails from the Mail server to a large number of recipients.

This IP belongs to Phillips 66.

It sent Asterisk requests to non-existent extensions.

Executed email spoofing attempts pretending to be a trusted party.

The said IP was the source of several rootkit deployment attempts.

It persistently tried to exploit weaknesses in the SSH communication encryption.

It attempted to perform a man-in-the-middle attack on the IMAP server.

The IP made multiple requests using uncommon HTTP methods.

It repeatedly attempted to run server-side injection attacks, trying to execute malicious code on our server.

It attempted to use the FTP server to distribute virus creation tools.

Multiple login attempts using common or easily guessable passwords (like 'password123', 'admin', etc.).

It was flagged that this IP had been used in conducting method tampering on our servers.

This IP belongs to Alphabet.

The IP attempted the notorious Shellshock vulnerability, which could pose a severe threat to our server's resources.

This IP belongs to Heroku.

It partook in location spoofing, making it appear from different locations.

This IP belongs to Vodafone.

The IP was seen engaging in a Slowloris attack, holding as many connections to the target web server open for as long as possible, eventually overloading the server.

Repeated HTTP requests with error codes, indicating failed attempts to access restricted areas.