Sent one malformed HTTP request with a suspicious header to our internet-facing service on port 80, ...
show moreSent one malformed HTTP request with a suspicious header to our internet-facing service on port 80, received HTTP 444 (connection closed) back.
Target: HTTP 80, GET / with a suspicious/malformed HTTP header
Seen: 2026-10-29 17:21 EDT
- 2026-10-29 17:21:54 external TCP client to :80 flagged by the flow sensor as 'HTTP Susp. Header' carrying a malformed HTTP header
- 2026-10-29 17:21:47 the request returned HTTP 444 (connection closed, empty body) from the responding web service
show less
Sent one malformed HTTP request with a suspicious header to our internet-facing service on port 80, ...
show moreSent one malformed HTTP request with a suspicious header to our internet-facing service on port 80, received HTTP 444 (connection closed) back.
Target: HTTP 80, GET / with a suspicious/malformed HTTP header
Seen: 2026-10-29 17:26 EDT
- 2026-10-29 17:26:03 external TCP client to :80 flagged by the flow sensor as 'HTTP Susp. Header' carrying a malformed HTTP header
- 2026-10-29 17:25:56 the request returned HTTP 444 (connection closed, empty body) from the responding web service
show less
Automated PHP-webshell scan of an internet-facing WordPress site: ~25 rapid backdoor probes over ~2 ...
show moreAutomated PHP-webshell scan of an internet-facing WordPress site: ~25 rapid backdoor probes over ~2 seconds, all returning 404/403/500.
Target: HTTPS 443, PHP webshell/backdoor paths (txets.php, wp-admin/php8.php, goods.php, wp-editor.php, wp-mail.php, /wp-content/plugins/fix/up.php)
Seen: 2026-10-29 16:21 EDT
- 16:21:51 GET /txets.php HTTP/2.0 -> 404 via Go-http-client/2.0
- 16:21:57 GET /wp-admin/php8.php HTTP/2.0 -> 403
- 16:21:42 GET /ioxi-o.php -> 404, 16:21:46 GET /wp-editor.php -> 404, 16:21:55 GET /goods.php -> 404 (25+ similar probes in 16:21:26-16:21:58)
show less
Single connection from an Alibaba Cloud Hangzhou data-center host to the public HTTPS port 443, flag ...
show moreSingle connection from an Alibaba Cloud Hangzhou data-center host to the public HTTPS port 443, flagged as a malicious traffic fingerprint; no service response followed.
Target: HTTPS 443, connection attempt from a known-bad Alibaba Cloud scanner
Seen: 2026-10-29 15:29 EDT
- 2026-10-29 15:29:56 - a connection from 47.99.240.206:46439 to the public HTTPS port 443 was flagged as a malicious traffic fingerprint
- 47.99.240.206 is an Alibaba Cloud Hangzhou data-center host (AS37963) with repeated port-scan, web-attack and hacking reports
show less
Rapid automated path-enumeration attack against the public HTTP site in about 9 seconds - dozens of ...
show moreRapid automated path-enumeration attack against the public HTTP site in about 9 seconds - dozens of GET requests to login, register, a host, dashboard and admin paths, mostly 404.
Target: HTTP 80 (site kimberlymackdesign.com), paths /login, /register, /a host/login, /a host/register, /password/reset, /forgot-password, /admin, /admin/login, /dashboard, /pulse, /filament, /nova, /live...
Seen: 2026-10-29 15:37 EDT
- 2026-10-29 15:37:21-15:37:29 - roughly 40 GET requests from one source in about 9 seconds against many web paths
- Most paths returned HTTP 404, e.g. /login, /register, /a host/login, /a host/register, /password/reset, /forgot-password, /admin, /admin/login, /admin/users, /admin/settings, /admin/orders, /admin/products, /admin/reports, /dashboard, /home, /pulse, /filament, /nova, /horizon, /telescope, /user/profile, /settings, /account
- Livewire AJAX endpoints also probed and 404'd, e.g. /register/livewire/update, /login/livewire/update, /livewire/update
show less
Known internet-scan host (rDNS internet-census.org.
Target: HTTPS 443, connection attempt from a kno ...
show moreKnown internet-scan host (rDNS internet-census.org.
Target: HTTPS 443, connection attempt from a known internet-scan host
Seen: 2026-10-29 12:44 EDT
- 2026-10-29 12:44:29 the flow from this source to the public HTTPS service on port 443 was classified a Malicious Fingerprint (Emergency severity)
- 2026-10-29 12:44:24 a single TCP SYN from this source reached the perimeter HTTPS port 443 as a pass, with no service response following (single-flow probe)
- rDNS resolves to sh-ams-nl-gp7-wk103a.internet-census.org (Netherlands, AS211680), consistent with an automated internet port-scanning host
show less
Abused Amazon EC2 host (rDNS compute-1.amazonaws.com.
Target: HTTP 80, connection attempt from an ab ...
show moreAbused Amazon EC2 host (rDNS compute-1.amazonaws.com.
Target: HTTP 80, connection attempt from an abused Amazon EC2 host
Seen: 2026-10-29 12:16 EDT
- 2026-10-29 12:16:29 the flow from this source to the public HTTP service on port 80 was classified a Malicious Fingerprint (Emergency severity)
- 2026-10-29 12:16:23 a single TCP SYN from this source reached the perimeter HTTP port 80 as a pass, with no service response following (single-flow probe)
show less
Known internet-scan host (rDNS internet-census.org, Zenlayer.
Target: HTTP 80, connection attempt fr ...
show moreKnown internet-scan host (rDNS internet-census.org, Zenlayer.
Target: HTTP 80, connection attempt from a known internet-scan host
Seen: 2026-10-29 12:38 EDT
- 2026-10-29 12:38:18 the flow from this source to the public HTTP service on port 80 was classified a Malicious Fingerprint (Critical severity)
- 2026-10-29 12:38:13 a single TCP SYN from this source reached the perimeter HTTP port 80 as a pass, with no service response following (single-flow probe)
- rDNS resolves to zl-dfwc-us-gp7-wk111b.internet-census.org (US, Zenlayer AS21859), consistent with an automated internet port-scanning host
show less
Attack traffic from this IP.
Target: SYN-only probe from external 201.55.162.78
Seen: 2026-10-29 11: ...
show moreAttack traffic from this IP.
Target: SYN-only probe from external 201.55.162.78
Seen: 2026-10-29 11:32 EDT
- Critical Malicious Fingerprint flow at 2026-10-29T15:32:19Z: 201.55.162.78:41140 -> port 443 (single flow, no application response)
- Firewall at 2026-10-29 11:32:13: single TCP SYN (S) pass on tcp/443 from 201.55.162.78:41140 to port 443 on the WAN edge
show less
Google Cloud VPS probing the internet-facing service for exposed secret files (.env) โ recurring rec ...
show moreGoogle Cloud VPS probing the internet-facing service for exposed secret files (.env) โ recurring recon (also seen last hour) against the ai.* host.
Target: HTTPS 443, GET /.env.save and /.env.backup on the ai.* vhost
Seen: 2026-10-29 10:33 EDT
- 2026-10-29 10:33:10 - GET /.env.save HTTP/1.1 returned 403 from 34.131.209.171 against the ai.* service
- 2026-10-29 10:33:10 - GET /.env.backup HTTP/1.1 returned 403 from 34.131.209.171 against the same service
show less
Port-scan/SSH/hacking reputation) matched as a Malicious Fingerprint striking the edge HTTPS service ...
show morePort-scan/SSH/hacking reputation) matched as a Malicious Fingerprint striking the edge HTTPS service.
Target: HTTPS 443, connection attempt from a known-bad Alibaba Cloud scanner
Seen: 2026-10-29 10:09 EDT
- 2026-10-29 10:09:27 - classified a flow from 47.110.155.130:47562 to the edge HTTPS port 443 as a Malicious Fingerprint (Emergency severity)
- 2026-10-29 10:09:19 - a TCP SYN from 47.110.155.130 to edge port 443 was seen reaching the public service
show less
17 reports of env/.git/phpinfo probing) hammering the edge web server with empty User-Agent requests ...
show more17 reports of env/.git/phpinfo probing) hammering the edge web server with empty User-Agent requests.
Target: HTTP 80, GET / with empty User-Agent from a PrivateByte scanner
Seen: 2026-10-29 10:45 EDT
- 2026-10-29 10:45:38-39 - multiple GET / requests returned HTTP 444 with an empty User-Agent from 87.232.92.96 to edge port 80
- 2026-10-29 10:45:44 - flagged 87.232.92.96 for an HTTP suspicious (empty) User-Agent flow against the edge
- 2026-10-29 10:45:39 - rapid multi-port TCP connection attempts from 87.232.92.96 (src ports 40166-40206) to edge port 80
show less
Tencent Cloud (Shanghai) IP sending bare TCP SYN probes to the internet-facing edge on TCP 80/443/89 ...
show moreTencent Cloud (Shanghai) IP sending bare TCP SYN probes to the internet-facing edge on TCP 80/443/8980 โ no completed handshake, automated port scanning flagged by the traffic sensor.
Target: TCP 80, 443 and 8980 on the internet edge (bare SYN probes, no handshake)
Seen: 2026-10-29 08:49 EDT
- 08:49:20 โ bare TCP SYN from 110.42.134.231:5737 to port 80, no completed handshake
- 08:49:20 โ bare TCP SYN from 110.42.134.231:26500 to port 443, no completed handshake
- 08:49:20 โ bare TCP SYN from 110.42.134.231:16040 to port 8980, blocked at the edge
- 08:49:25 โ traffic sensor flagged both the port-80 and port-443 flows as a Malicious Fingerprint (Critical)
show less
Google Cloud IP running an automated port scan against the edge on TCP 80 and 443, sending bare SYN ...
show moreGoogle Cloud IP running an automated port scan against the edge on TCP 80 and 443, sending bare SYN probes with no completed handshake and no data returned.
Target: Bare TCP SYN port scan
Seen: 2026-10-29 07:57-07:58 EDT
- 2026-10-29 07:58:05 EDT: one bare TCP SYN to the edge on TCP 80 (source port 59538); no handshake completed, no bytes returned
- 2026-10-29 07:57:57 EDT: an earlier bare TCP SYN from the same source port 59554 to the same edge port 80, repeated SYN-only probe
show less
HostUS data-center IP repeatedly sending bare TCP SYN probes to the edge on TCP 443 with no complete ...
show moreHostUS data-center IP repeatedly sending bare TCP SYN probes to the edge on TCP 443 with no completed handshake โ automated reconnaissance.
Target: Bare TCP SYN port scan
Seen: 2026-10-28 18:31 EDT to 2026-10-29 07:42 EDT
- 2026-10-29 07:42:43 EDT: one bare TCP SYN to the edge on TCP 443 (source port 39674); no handshake, no bytes returned
- 2026-10-28 18:31 EDT: an earlier TCP SYN from the same address to TCP 443, dropped before a handshake formed
show less
Sustained CMS/admin/a host path sweep against an internet-facing HTTPS host, every non-root path ret ...
show moreSustained CMS/admin/a host path sweep against an internet-facing HTTPS host, every non-root path returning 404.
Target: Vhost kimberlymackdesignstudio.com), sweep of CMS/admin/a host discovery paths
Seen: 2026-10-29 05:31 EDT
- 2026-10-29 05:31:25 to 05:31:33 - about 35 requests sweeping CMS/admin/a host paths against vhost kimberlymackdesignstudio.com, all returning HTTP 404
- 2026-10-29 05:31:27 to 05:31:33 - livewire/update AJAX endpoints probed (/register/livewire/update, /login/livewire/update, /livewire/update, /admin/login/livewire/update), all 404
- 2026-10-29 05:31:28 - GET / returned HTTP 200 (1918 bytes) to the same source
- User-agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 was identical across every probe in the burst
show less
Google Cloud (Ghostfleet botnet) host sent protocol-confusion requests (binary MongoDB-style admin.$ ...
show moreGoogle Cloud (Ghostfleet botnet) host sent protocol-confusion requests (binary MongoDB-style admin.$cmd payload) to internet-facing HTTP port 80; all rejected with 400.
Target: HTTP 80, protocol-confusion payload (binary MongoDB admin.$cmd shell command)
Seen: 2026-10-29 03:38-04:38 EDT
- 03:38:17 protocol-confusion request to HTTP :80 with raw MongoDB admin.$cmd payload body, returned 400
- 03:38:12-03:38:19 repeated malformed/missing-protocol requests to HTTP :80, all rejected with 400
- 04:38:14 IDS 'HTTP request missing protocol' signature from same source, port 80
show less
Known WordPress scanner/brute-forcer hitting a WordPress site with admin, plugin-exploit, and login ...
show moreKnown WordPress scanner/brute-forcer hitting a WordPress site with admin, plugin-exploit, and login probes; all requests rejected (403/400).
Target: HTTP WordPress app โ /wp-admin/admin-ajax.php wdpsso_step1 exploit, /wp-json, /wp-login.php
Seen: 2026-10-29 02:13 EDT
- 02:13:21 GET /wp-admin/admin-ajax.php?action=wdpsso_step1&redirect= 400 from 161.118.209.40
- 02:13:20 POST /wp-json/batch/v1 207 from 161.118.209.40
- 02:13:23 POST /wp-admin/admin-ajax.php?meta-box-loader=1 403 from 161.118.209.40
show less
Web-application scanner hammering a WordPress site with rapid admin/login-page probes.
Target: HTTP/ ...
show moreWeb-application scanner hammering a WordPress site with rapid admin/login-page probes.
Target: HTTP/HTTPS web app login and admin pages
Seen: 2026-10-29 02:26-02:27 EDT
- 02:26:53 GET /wp-login.php HTTP/2.0 403 from 195.178.110.155
- 02:26:57 GET /register HTTP/2.0 404 from 195.178.110.155
- 02:26:58 GET /forgot-password HTTP/2.0 404 from 195.178.110.155
- 02:26:59 GET /a host/register HTTP/2.0 404 from 195.178.110.155, triggering IDS alert 'Sustained web attack from known-hostile source'
- Rush of ~15 requests between 02:26:53 and 02:26:59 including /login, /admin/login, /login/livewire/update, /register/livewire/update
show less
HIT the site's WordPress vhosts with a wlwmanifest.xml recon sweep across many path variants plus an ...
show moreHIT the site's WordPress vhosts with a wlwmanifest.xml recon sweep across many path variants plus an xmlrpc.php?rsd check, all returning 404.
Target: HTTP/HTTPS, GET //wp-includes/wlwmanifest.xml (site, cms, wp1, wp2, media, shop, blog, wordpress, news, 2018, 2019 variants) and //xmlrpc.php?rsd
Seen: 2026-10-28 03:17 EDT
- 03:17:24-03:17:27 - 24 requests for //wp-includes/wlwmanifest.xml across variants (//site, //cms, //wp1, //wp2, //media, //shop, //blog, //wordpress, //news, //2018, //2019), each HTTP 404, user-agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/78.0.3904.108
- 03:17:25 - GET //xmlrpc.php?rsd returned HTTP 404
show less
Brute-forced WordPress /wp-login.php (POST and GET, blocked 403 at the edge) and enumerated users vi ...
show moreBrute-forced WordPress /wp-login.php (POST and GET, blocked 403 at the edge) and enumerated users via /wp-json/wp/v2/users/me (unauthenticated, 401).
Target: HTTPS 443, POST and GET /wp-login.php and GET /wp-json/wp/v2/users/me
Seen: 2026-10-28 03:08 EDT
- 03:08:14-03:08:16 - POST /wp-login.php and GET /wp-login.php each returned HTTP 403 (3 attempts each), user-agent Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Firefox/148.0
- 03:08:12-03:08:17 - GET /wp-json/wp/v2/users/me returned HTTP 401 (3 attempts, un authenticated)
show less
Web App Attack
By clicking โAccept allโ, you agree to the storing of cookies on your device to remember preferences and
analyze site usage.
Read more
- Required to log into your AbuseIPDB account, and store these cookie preferences.