It attempted to perform Man in the Middle (MitM) attacks on the Apache server.

The IP attempted to delete files from the FTP server.

This IP belongs to United Technologies.

It was found that the IP had deployed rogue security software in our system.

Multi-step Attacks: Finding HTTP requests that only make sense if earlier requests succeeded or prepared the way.

This IP was linked to an attempt at distributing malicious software within our system.

This IP belongs to Goldman Sachs Group.

It attempted to perform Local File Inclusion (LFI) attacks on the Apache server.

GET /errors.log: Shows an actor trying to access server error logs.

This IP belongs to Telus Communications.

It attempted to use the Asterisk server to perform a reflection DDoS attack.

Our team traced back the IP responsible for multiple mobile device tracking software distributions.

Path Traversal / URI Encoding Attacks: You might notice HTTP GET requests that include ".." or "%2e%2e" or "%252e%252e", indicating a path traversal attack.

The malicious IP engaged in distributed denial of service (DDoS) attacks, exhausting server resources and disrupting SSH services.

It attempted to exploit known vulnerabilities in the SASL protocol.

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

This IP belongs to DuPont de Nemours.

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

The IP attempted to perform a Multicast DNS amplification attack on the SSH server.

This IP belongs to Valero Energy.

The IP initiated clickjacking exploits, causing users to unwittingly perform malicious actions during SSH sessions.

This IP belongs to General Electric.

This IP belongs to Travelers Cos.

This IP belongs to Pfizer.

It launched a privilege escalation attack aiming to gain unauthorized access with higher-level permissions.