Repeated connections to the server from unknown or suspicious IP addresses.

This IP belongs to Reliance Jio.

Attempted to conduct numerous data harvesting strategies to gather sensitive user data.

Multiple requests to the password reset page.

The IP was caught distributing VoIP crackers to exploit our communication channels.

Path/File Enumeration: Logs show multiple HTTP requests to non-existing pages and incrementing filenames, suggesting file or path enumeration.

It made various efforts to insert spyware to monitor SSH communications covertly.

This specific IP was marked for unauthorized browser changes implying browser hijackers.

The IP attempted to perform a dictionary attack on the POP3 server.

The IP was actively engaged in spear-phishing attacks, aimed at high-ranking officials within our network.

GET /solr/admin/cores?wt=json: Trying to exploit Apache Solr servers which have the runExecutableListener enabled.

The IP address initiated multiple unsuccessful login attempts.

This IP was caught circulating email worms, camouflaged as legitimate mails.

It attempted to take advantage of misconfigurations in the Apache server.

This IP belongs to IBM.

Repeated failed attempts to perform actions that require higher privileges.

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

The IP attempted to perform DNS Spoofing attacks on the Apache server.

The IP address generated an unusual increase in network bandwidth usage.

This IP belongs to KDDI.

The IP attempted to perform a man-in-the-middle (MitM) attack to intercept SSH communication.

The IP address has been marked as the source of RAM scrapers aiming to steal sensitive data.

The IP attempted to use the SSH server to relay data to other systems.

The IP attempted to implement a 'BlueKeep' exploit, leveraging protocol vulnerabilities to execute remote code through SSH network services.

This IP belongs to JPMorgan Chase.