34.104.139.49

Blocked Brute Toolkit

Blocked since 13 Oct 2026 10:47 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: Persistent
Attack-shaped requests: 250all time
Active days: 1UTC days
First seen: 13 Oct 2026
Last seen: 13 Oct 2026 10:45
Servers hit: 2
Targets: 1site
Times blocked: 0by the evidence rules

First seen on 13 Oct 2026 10:44 UTC, most recently active on 13 Oct 2026 10:45 UTC.

Recorded 250 attack-shaped requests across 1 separate day.

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

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

Its busiest hour on record began 13 Oct 2026 10:00 UTC, with 250 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: 13 Oct 2026, with no end date.

Daily counts

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

At least 241 requests a minute at its peak (13 Oct 2026 10:44 UTC; identical requests in the same second are stored once).
Methods: GET 261.
The servers we watch answered: 404 248, 200 8, 403 6 (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
13 Oct 2026
10:45	zmey.eu	2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)	`GET /cgi-bin/php?`	declared bot	web
10:45	zmey.eu	fuzzed a short, random filename looking for a forgotten script that responds	`GET /index.php?`	declared bot	web
10:45	zmey.eu	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
10:45	zmey.eu	made a request that matched no known pattern	`GET /cgi-bin/php-cgi.exe`	declared bot	web
10:45	zmey.eu	fuzzed a short, random filename looking for a forgotten script that responds	`GET /index.php?`	declared bot	web
10:45	zmey.eu	probed a Next.js/Auth.js (NextAuth) authentication route, consistent with fingerprinting a Next.js app's auth stack	`GET /api/auth`	declared bot	web
10:45	zmey.eu	probed a list of common site paths looking for an unprotected admin panel or staging copy	`GET /admin`	declared bot	web
10:45	zmey.eu	2× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner (2 distinct paths)	`GET /dashboard`	declared bot	web
10:44	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /.env`	declared bot	edge
10:44	zmey.eu	swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner	`GET /login`	declared bot	web
10:44	zmey.eu	7× requested a .env file, hoping to find API keys or database credentials (6 distinct paths)	`GET /@fs/.env?`	declared bot	web
10:44	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/orders/..%2F..%2Fproc/self/environ`	declared bot	web
10:44	zmey.eu	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
10:44	zmey.eu	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /.env.production?`	declared bot	web
10:44	zmey.eu	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
10:44	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /.env.local?`	declared bot	web
10:44	zmey.eu	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
10:44	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/proc/self/cwd/.env?`	declared bot	web
10:44	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/orders/..%2F..%2F.env`	declared bot	web
10:44	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /packages/.env`	declared bot	web
10:44	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/orders/..%2Fadmin/config.json`	declared bot	web
10:44	zmey.eu	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /.env.local?`	declared bot	web
10:44	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /api/data/..%2F..%2F.env`	declared bot	web
10:44	zmey.eu	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /@fs/var/task/.env?`	declared bot	web
10:44	zmey.eu	requested an AWS credentials file left in a web-accessible path by mistake	`GET /@fs/home/ec2-user/.aws/credentials?`	declared bot	web
10:44	zmey.eu	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
10:44	zmey.eu	2× requested an AWS credentials file left in a web-accessible path by mistake (2 distinct paths)	`GET /@fs/home/ubuntu/.aws/credentials?`	declared bot	web
10:44	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /@fs/..%252f..%252f..%252f..%252f..%252fproc/self/environ?`	declared bot	web
10:44	zmey.eu	3× used Vite dev server's @fs/ path to try to read arbitrary files outside the project root (3 distinct paths)	`GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?`	declared bot	web
10:44	zmey.eu	2× requested a decoy path that only a scanner would ask for (2 distinct paths)	`GET /.env?`	browser claim	web
10:44	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /@fs/..%252f..%252f..%252f..%252f..%252froot/.env?`	declared bot	web
10:44	zmey.eu	requested a private SSH key file by its conventional name	`GET /id_rsa`	declared bot	web
10:44	zmey.eu	tried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flaw	`GET /@fs/proc/self/environ?`	declared bot	web
10:44	zmey.eu	made a request that matched no known pattern	`GET /%2Fapi/config`	declared bot	web

Network

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