It was flagged initiating reflective (DRDoS) attacks, intending to exhaust our server resources.

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

We linked several cryptojacking attempts, aimed at harnessing our system resources, to this IP.

The IP made multiple requests using uncommon HTTP methods.

The IP was detected attempting to skirt our system's detection through spoofing.

The IP made multiple unsuccessful login attempts to the SSH server in a short period of time.

The IP attempted a race condition attack, aiming to execute unwanted sequences in the server.

GET /trace.axd: An attempt to find a debug handler in ASP.NET.

Inclusion of Binary Data in HTTP Request: If binary data is included in the HTTP request, this could suggest an attacker is attempting a binary exploit.

It was responsible for an unusual increase in server CPU usage.

This IP belongs to Morgan Stanley.

The IP attempted to manipulate trusted authorities by conducting SSL strip attacks.

The malicious IP attempted ARP spoofing to fool the server into sending information to the wrong destination.

It exploited CVE-specific server vulnerabilities as a backdoor entrance to our mail system.

The IP attempted to launch Ciphertext attacks, trying to decrypt SSH-encrypted communication.

The IP attempted to use the FTP server to distribute malware.

This IP belongs to Boeing.

IP Spoofing: Logs showing HTTP requests with IP ranges that are typically reserved for private networks or an unusual X-Forwarded-For header.

It attempted to exploit known vulnerabilities in the SSH protocol.

The IP has been caught trying to deliver spyware into our system to compromise sensitive data.

The IP attempted to use the Mail server to relay emails with misleading headers to other servers.

This IP belongs to Marathon Petroleum.

The IP attempted to use the Mail server to relay spam to other servers.

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

This IP belongs to Exxon Mobil.