Alert queue
Connecting…
| Severity | Category | Source IP | Sensor | Reasoning | Received |
|---|---|---|---|---|---|
| S4 | successful_intrusion | 101.96.192.198 | hp-use-01 | The session shows a successful SSH login to the honeypot using the root account, which constitutes a foothold. Per rubric, any successful login is at least seve | |
| S4 | successful_intrusion | 185.100.85.24 | hp-use-01 | The session includes a successful SSH login using root/admin after one failed attempt, which establishes a foothold on the honeypot. Per rubric, any successful | |
| S4 | successful_intrusion | 195.178.110.228 | hp-use-01 | The session shows a successful SSH login to the Cowrie honeypot using root/123123. Per rubric, any successful login is a foothold and maps to severity 4 with ca | |
| S4 | successful_intrusion | 195.178.110.228 | hp-use-01 | The session shows a successful SSH login to the honeypot using root/111111, which establishes a foothold and meets the severity-4 threshold. Per tool output, no | |
| S4 | successful_intrusion | 195.178.110.228 | hp-use-01 | A successful SSH login occurred using root/!root, which constitutes a foothold on the honeypot. Per the rubric, any successful login is at least severity 4 and | |
| S4 | successful_intrusion | 121.128.162.194 | hp-use-01 | The session includes a successful SSH login using root/admin after one failed attempt. Per rubric, any successful login constitutes a foothold even if no post-l | |
| S4 | successful_intrusion | 2.57.122.168 | hp-use-01 | The session shows a successful SSH login to the Cowrie honeypot using root/!root. Per the rubric, any successful login constitutes a foothold and maps to succes | |
| S4 | successful_intrusion | 8.138.104.242 | hp-use-01 | The session shows a successful SSH login using root/password after one failed attempt. Per rubric, any successful login constitutes a foothold and maps to succe | |
| S4 | successful_intrusion | 195.178.110.227 | hp-use-01 | The session achieved a successful SSH login using root/1234, which constitutes a foothold on the honeypot. Tool output confirms there were no post-login command | |
| S4 | successful_intrusion | 195.178.110.227 | hp-use-01 | The session shows a successful SSH login to the honeypot using root/123, which constitutes a foothold. Per the rubric, any successful login is at least severity | |
| S4 | successful_intrusion | 119.97.184.93 | hp-use-01 | The session shows a successful SSH login using root/ubuntu, which establishes a foothold on the honeypot. Per rubric, any successful login is at least severity | |
| S4 | successful_intrusion | 112.17.140.107 | hp-use-01 | A successful SSH login occurred using credential pair root/ubuntu, which establishes a foothold on the honeypot. Per rubric, any successful login is at least se | |
| S4 | successful_intrusion | 2.57.122.150 | hp-use-01 | The session shows a successful SSH login using root:123, which constitutes a foothold on the honeypot. Per rubric, any successful login is at least severity 4 a | |
| S4 | successful_intrusion | 2.57.122.150 | hp-use-01 | A successful SSH login occurred using root/111111, which establishes a foothold and meets severity 4 by rubric. Retrieved session commands show no post-login co | |
| S4 | successful_intrusion | 2.57.122.150 | hp-use-01 | The session shows a successful SSH login to the honeypot using root/000000, which constitutes a foothold. Per the rubric, any successful login is at least sever | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using credential pair ssh/ssh, which establishes a foothold and meets the severity-4 threshold. Per tool output, there | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using the credential pair user/user. Per rubric, any successful login constitutes a foothold and maps to successful_int | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using credential pair admin/user2, which constitutes a foothold on the honeypot. Per rubric, any successful login is at | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using admin:user, which establishes a foothold. Per the rubric, any successful login is at least severity 4 and falls u | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using credential pair admin/user1. Per rubric, any successful login constitutes a foothold and maps to successful_intru | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | A successful SSH login occurred using admin/admin, which establishes a foothold and meets the severity-4 rubric. Retrieved session commands show no post-login c | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using admin:test, which constitutes a foothold on the honeypot. Per rubric, any successful login is at least severity 4 | |
| S4 | successful_intrusion | 151.243.18.193 | hp-use-01 | The session shows a successful SSH login using default-style credentials (admin/password). Per rubric, any successful login constitutes a foothold and maps to s | |
| S4 | successful_intrusion | 77.239.124.157 | hp-use-01 | The session shows a successful SSH login to the honeypot using root with password 123123asd. Per rubric, any successful login constitutes a foothold and maps to | |
| S4 | successful_intrusion | 77.239.124.157 | hp-use-01 | The session shows a successful SSH login using username 'rdpuser' with password '1234', which establishes a foothold and meets the severity-4 threshold. Per com |