8.234.214.137

Blocked Persistent Toolkit

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

Record

Score: 47/100each request counts half as much after 30 days
Worst level: Persistent
Attack-shaped requests: 260all time
Active days: 1UTC days
First seen: 17 Oct 2026
Last seen: 17 Oct 2026 09:08
Servers hit: 2
Targets: 1site
Times blocked: 0by the evidence rules

First seen on 17 Oct 2026 09:08 UTC, most recently active on 17 Oct 2026 09:08 UTC.

Recorded 260 attack-shaped requests across 1 separate day.

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

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

Scored into the "Persistent" level, its highest so far. Badge: Toolkit.

Its busiest hour on record began 17 Oct 2026 09:00 UTC, with 260 requests.

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

Surfaces: honeypot, 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
17 Oct 2026	260

At least 260 requests a minute at its peak (17 Oct 2026 09:08 UTC; identical requests in the same second are stored once).
Methods: GET 255, POST 15.
The servers we watch answered: 404 247, 200 5, 403 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
17 Oct 2026
09:08	4emx.com	5× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (5 distinct paths)	`POST /admin`	declared bot	edge
09:08	4emx.com	2× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner	`POST /api`	declared bot	web
09:08	4emx.com	requested the .git directory itself, hoping it is exposed and browsable	`/.git`	none	web
09:08	4emx.com	triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt	`POST /app`	declared bot	edge
09:08	4emx.com	probed for an exposed .git directory to download the site's source history and config	`GET /.git/config`	declared bot	edge
09:08	4emx.com	2× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (2 distinct paths)	`POST /api/route`	declared bot	edge
09:08	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	edge
09:08	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /pkg/.env`	declared bot	web
09:08	4emx.com	2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)	`GET /docker-compose.yml`	declared bot	web
09:08	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /userfiles/x?`	declared bot	web
09:08	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /secrets.env`	declared bot	web
09:08	4emx.com	2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /userfiles?`	declared bot	web
09:08	4emx.com	2× 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 (2 distinct paths)	`GET /credentials.json`	declared bot	web
09:08	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /userfiles/x?`	declared bot	web
09:08	4emx.com	3× 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 (3 distinct paths)	`GET /secrets.yml`	declared bot	web
09:08	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /userfiles?`	declared bot	web
09:08	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
09:08	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /dist/.env`	declared bot	web
09:08	4emx.com	2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)	`GET /cache/original/%2e%2e/.env`	declared bot	web
09:08	4emx.com	requested an AWS credentials file left in a web-accessible path by mistake	`GET /.aws/credentials`	declared bot	web
09:08	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /api/system/fileView?`	declared bot	web
09:08	4emx.com	probed for an exposed .git directory to download the site's source history and config	`GET /.git/HEAD`	declared bot	web
09:08	4emx.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /api/fs/read?`	declared bot	web
09:08	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 /.aws/config`	declared bot	web
09:08	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
09:08	4emx.com	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /build/.env`	declared bot	web
09:08	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 /var/run/secrets/kubernetes.io/serviceaccount/token`	declared bot	web
09:08	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/w/starter/jobs_u/get_log_file/../../../../proc/self/environ`	declared bot	web
09:08	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /frontend/.env`	declared bot	web
09:08	4emx.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/w/default/jobs_u/get_log_file/../../../../proc/self/environ`	declared bot	web
09:08	4emx.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /web/.env`	declared bot	web
09:08	4emx.com	2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)	`GET /api/w/admins/jobs_u/get_log_file/../../../../proc/self/environ`	declared bot	web
09:08	4emx.com	requested a .env file, hoping to find API keys or database credentials	`GET /app/.env`	declared bot	web

Network

ASN: AS396982 Google LLC
Network type: cloud
Reverse DNS: 137.214.234.8.bc.googleusercontent.com
Country: United States US
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.