34.81.10.184

Blocked Scanner Toolkit

Blocked since 17 Oct 2026 16:55 UTC, no end date. Our servers refuse it, web requests included, and it is in feed.txt.

Record

Score: 43/100each request counts half as much after 30 days
Worst level: Brute
Attack-shaped requests: 175all time
Active days: 1UTC days
First seen: 1 Oct 2026
Last seen: 1 Oct 2026 15:43
Servers hit: 2
Targets: 1site
Times blocked: 1by the evidence rules

First seen on 1 Oct 2026 15:43 UTC, most recently active on 1 Oct 2026 15:43 UTC.

Recorded 175 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (56 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (28); it also requested a common cloud/app secrets or credentials filename (AWS, GCP, Firebase, Kubernetes service-account token, SSH, master key) from a wordlist, hoping one was left in the webroot (13).

Seen by our edge and web sensors, against 4emx.com.

Scored into the "Scanner" level now; the highest it has reached is "Brute". Badge: Toolkit.

Its busiest hour on record began 1 Oct 2026 15:00 UTC, with 175 requests.

Routed via AS396982 (Google LLC), a cloud network.

Surfaces: web-app. Attack types: fake crawlers, known exploits, injection, scanning, hunting for secrets. Seen by: edge, web.

Activity, last 90 days

Active on 1 of the last 90 UTC days. Current block: 17 Oct 2026, with no end date.

Daily counts

Attack requests per UTC day, days with activity only
Day (UTC)	Requests
1 Oct 2026	175

At least 175 requests a minute at its peak (1 Oct 2026 15:43 UTC; identical requests in the same second are stored once).
Methods: GET 159, POST 11.
The servers we watch answered: 404 98, 301 60, 403 12, 400 5 (totals only, from our web servers).

Evidence

Newest first, the latest 50 stored requests grouped into runs. Times are UTC. The user agent is shown as its family only.

Evidence, newest first, grouped by UTC day
Time	Site	What happened	Request	User agent	Seen by
1 Oct 2026
15:43	4emx.com	claimed to be Googlebot while POSTing, something the real crawler never does	`POST /exec-py`	declared bot	web
15:43	4emx.com	attempted the Apache 2.4.49 cgi-bin path-traversal exploit to read or execute files outside the web root (CVE-2021-41773)	`POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`GET /cgi-bin/php?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`POST /cgi-bin/php?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`GET /cgi-bin/php-cgi?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`POST /cgi-bin/php-cgi?`	declared bot	web
15:43	4emx.com	fuzzed a short, random filename looking for a forgotten script that responds	`GET /index.php?`	declared bot	web
15:43	4emx.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /index.php?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`GET /cgi-bin/php?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`POST /cgi-bin/php?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`GET /cgi-bin/php-cgi.exe?`	declared bot	web
15:43	4emx.com	tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code	`POST /cgi-bin/php-cgi.exe?`	declared bot	web
15:43	4emx.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`GET /php-cgi/php-cgi.exe?`	declared bot	web
15:43	4emx.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /php-cgi/php-cgi.exe?`	declared bot	web
15:43	4emx.com	fuzzed a short, random filename looking for a forgotten script that responds	`GET /index.php?`	declared bot	web
15:43	4emx.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /index.php?`	declared bot	web
15:43	4emx.com	claimed to be Googlebot while POSTing, something the real crawler never does	`POST /api/designer/v1/file-content`	declared bot	web
15:43	4emx.com	probed a Spring Boot actuator endpoint, which can leak environment variables and internal config if left open	`GET /actuator/gateway/routes`	declared bot	web
15:43	4emx.com	probed a Spring Boot actuator endpoint, which can leak environment variables and internal config if left open	`GET /actuator/gateway/routes`	declared bot	web
15:43	4emx.com	swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner	`GET /api/v1/loginmethod?`	declared bot	web
15:43	4emx.com	requested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated	`GET /api/v1/configs`	declared bot	web
15:43	4emx.com	probed a list of common site paths looking for an unprotected admin panel or staging copy	`GET /admin`	declared bot	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/app/.env?`	declared bot	web
15:43	4emx.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/proc/self/cmdline?`	declared bot	web
15:43	4emx.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/proc/self/cmdline?`	declared bot	web
15:43	4emx.com	requested wp-config.php or a backup copy of it, hoping to read the database password in clear text	`GET /wp-config.php.bak`	declared bot	edge
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /settings%2F.env`	declared bot	web
15:43	4emx.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yaml`	declared bot	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /.env.development?`	declared bot	web
15:43	4emx.com	requested wp-config.php or a backup copy of it, hoping to read the database password in clear text	`GET /wp-config.php.bak`	declared bot	web
15:43	4emx.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yml`	declared bot	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /.env.development?`	declared bot	web
15:43	4emx.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?`	declared bot	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /api%2F.env`	declared bot	web
15:43	4emx.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yml`	declared bot	web
15:43	4emx.com	2× used Vite dev server's @fs/ path to try to read arbitrary files outside the project root (2 distinct paths)	`GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?`	declared bot	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /dashboard%2F.env`	declared bot	web
15:43	4emx.com	used the Grafana plugin path-traversal exploit to read files outside the intended directory (CVE-2021-43798)	`GET /public/plugins/text/../../../../../../../../proc/self/environ`	declared bot	web
15:43	4emx.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/token?`	declared bot	web
15:43	4emx.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /admin%2F.env`	declared bot	web
15:43	4emx.com	tried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flaw	`GET /icons/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/proc/self/environ`	declared bot	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /.env.development?`	declared bot	web
15:43	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /..%2f..%2f.env`	declared bot	web
15:43	4emx.com	2× requested a .env file, hoping to find API keys or database credentials	`/.env`	none	web
15:43	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/app/.env.production?`	declared bot	web
15:43	4emx.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /api/.env/public/.env`	declared bot	web

Network

ASN: AS396982 Google LLC
Network type: cloud
Reverse DNS: 184.10.81.34.bc.googleusercontent.com
Country: Taiwan TW
Flags: cloud range (GCP)
Abuse contact: found in the registry
Checked: 12 Oct 2026

Elsewhere: GreyNoise, Shodan, AbuseIPDB.

Your verdict

What readers make of this address. Verdicts are opinions of signed-in Academy members. They never change blocking or reporting.

No verdicts yet.