34.39.161.152

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: 46/100each request counts half as much after 30 days
Worst level: Brute
Attack-shaped requests: 383all time
Active days: 1UTC days
First seen: 30 Sep 2026
Last seen: 30 Sep 2026 16:49
Servers hit: 2
Targets: 1site
Times blocked: 1by the evidence rules

First seen on 30 Sep 2026 10:51 UTC, most recently active on 30 Sep 2026 16:49 UTC.

Recorded 383 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (136 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (93); 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 (45); 5 requests matched no known pattern.

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 30 Sep 2026 16:00 UTC, with 219 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
30 Sep 2026	383

At least 213 requests a minute at its peak (30 Sep 2026 16:48 UTC; identical requests in the same second are stored once).
Methods: GET 355, POST 22.
The servers we watch answered: 404 293, 301 49, 403 37, 400 9 (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
30 Sep 2026
16:49	4emx.com	2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)	`POST /cgi-bin/php?`	declared bot	web
16:49	4emx.com	fuzzed a short, random filename looking for a forgotten script that responds	`POST /index.php?`	declared bot	web
16:49	4emx.com	2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)	`POST /cgi-bin/php?`	declared bot	web
16:49	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
16:48	4emx.com	fuzzed a short, random filename looking for a forgotten script that responds	`POST /index.php?`	declared bot	web
16:48	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
16:48	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
16:48	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
16:48	4emx.com	claimed to be Googlebot while POSTing, something the real crawler never does	`POST /lib/terminal-xhr.php`	declared bot	web
16:48	4emx.com	3× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (3 distinct paths)	`POST /admin`	declared bot	edge
16:48	4emx.com	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	`GET /firebase-config.json`	declared bot	web
16:48	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /.env`	declared bot	web
16:48	4emx.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /.env.production`	declared bot	web
16:48	4emx.com	requested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated	`GET /api/config`	declared bot	web
16:48	4emx.com	requested a config.json file, hoping it exposes API keys or internal settings	`GET /config.json`	declared bot	web
16:48	4emx.com	7× 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 (7 distinct paths)	`GET /push_config.json`	declared bot	web
16:48	4emx.com	6× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)	`GET /userfiles/x?`	declared bot	web
16:48	4emx.com	made a request that matched no known pattern	`GET /api/system/fileView?`	declared bot	web
16:48	4emx.com	tried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flaw	`GET /api/system/fileView?`	declared bot	web
16:48	4emx.com	made a request that matched no known pattern	`GET /api/fs/read?`	declared bot	web
16:48	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /cache/original/%2e%2e/%2e%2e/.env`	declared bot	web
16:48	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /cache/original/%2e%2e/.env`	declared bot	web
16:48	4emx.com	tried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flaw	`GET /api/fs/read?`	declared bot	web
16:48	4emx.com	5× requested a .env file, hoping to find API keys or database credentials (5 distinct paths)	`GET /settings%2F.env`	declared bot	web
16:48	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/console/api_server?`	declared bot	web
16:48	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /pipeline/.env`	declared bot	web
16:48	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /document.php?`	declared bot	web
16:48	4emx.com	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /data/.env`	declared bot	web

Network

ASN: AS396982 Google LLC
Network type: cloud
Reverse DNS: 152.161.39.34.bc.googleusercontent.com
Country: Brazil BR
Flags: cloud range (GCP)
Abuse contact: found in the registry
Checked: 17 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.