Network Analysis
| Name | Response | Post-Analysis Lookup |
|---|---|---|
| api.telegram.org | 149.154.167.220 | |
| api.ipify.org |
CNAME
api4.ipify.org
|
64.185.227.155 |
GET
200
https://api.ipify.org/
REQUEST
RESPONSE
BODY
GET / HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0
Host: api.ipify.org
Connection: Keep-Alive
HTTP/1.1 200 OK
Content-Length: 15
Content-Type: text/plain
Date: Wed, 08 Feb 2023 09:44:44 GMT
Vary: Origin
ICMP traffic
No ICMP traffic performed.
IRC traffic
No IRC requests performed.
Suricata Alerts
| Flow | SID | Signature | Category |
|---|---|---|---|
| TCP 149.154.167.220:443 -> 192.168.56.103:49169 | 2029340 | ET INFO TLS Handshake Failure | Potentially Bad Traffic |
| UDP 192.168.56.103:50800 -> 164.124.101.2:53 | 2033966 | ET HUNTING Telegram API Domain in DNS Lookup | Misc activity |
| TCP 192.168.56.103:49169 -> 149.154.167.220:443 | 2033967 | ET HUNTING Observed Telegram API Domain (api .telegram .org in TLS SNI) | Misc activity |
| TCP 192.168.56.103:49169 -> 149.154.167.220:443 | 906200022 | SSLBL: Malicious JA3 SSL-Client Fingerprint detected (Tofsee) | undefined |
| TCP 192.168.56.103:49169 -> 149.154.167.220:443 | 2033967 | ET HUNTING Observed Telegram API Domain (api .telegram .org in TLS SNI) | Misc activity |
| TCP 192.168.56.103:49165 -> 104.237.62.211:443 | 906200022 | SSLBL: Malicious JA3 SSL-Client Fingerprint detected (Tofsee) | undefined |
| TCP 192.168.56.103:49169 -> 149.154.167.220:443 | 2033967 | ET HUNTING Observed Telegram API Domain (api .telegram .org in TLS SNI) | Misc activity |
Suricata TLS
| Flow | Issuer | Subject | Fingerprint |
|---|---|---|---|
|
TLS 1.2 192.168.56.103:49165 104.237.62.211:443 |
C=GB, ST=Greater Manchester, L=Salford, O=Sectigo Limited, CN=Sectigo RSA Domain Validation Secure Server CA | CN=*.ipify.org | f4:76:2d:2c:65:d1:15:be:19:a4:c5:e0:8d:eb:89:1a:b6:75:4a:54 |
Snort Alerts
No Snort Alerts