136.107.82.203

Blocked Persistent Night Owl Toolkit

Blocked since 18 Oct 2026 02:28 UTC, no end date. Our servers refuse it, web requests included, and it is in feed.txt.

Record

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

First seen on 18 Oct 2026 02:27 UTC, most recently active on 18 Oct 2026 02:27 UTC.

Recorded 259 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 zmey.eu.

Scored into the "Persistent" level, its highest so far. Badges: Night Owl and Toolkit.

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

Daily counts

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

At least 259 requests a minute at its peak (18 Oct 2026 02:27 UTC; identical requests in the same second are stored once).
Methods: GET 253, POST 16.
The servers we watch answered: 404 245, 403 6, 200 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
18 Oct 2026
02:27	zmey.eu	claimed to be Googlebot while POSTing, something the real crawler never does	`POST /lib/file-control.php`	declared bot	web
02:27	zmey.eu	2× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (2 distinct paths)	`/app`	none	web
02:27	zmey.eu	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
02:27	zmey.eu	sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked	`/`	none	web
02:27	zmey.eu	requested the .git directory itself, hoping it is exposed and browsable	`/.git`	none	web
02:27	zmey.eu	6× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (6 distinct paths)	`POST /settings`	declared bot	edge
02:27	zmey.eu	probed for an exposed .git directory to download the site's source history and config	`GET /.git/config`	declared bot	edge
02:27	zmey.eu	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yaml`	declared bot	web
02:27	zmey.eu	requested .htaccess or .htpasswd, which can leak access rules or password hashes	`GET /.htpasswd`	declared bot	web
02:27	zmey.eu	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yml`	declared bot	web
02:27	zmey.eu	4× 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 (4 distinct paths)	`GET /credentials.json`	declared bot	web
02:27	zmey.eu	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /secrets.env`	declared bot	web
02:27	zmey.eu	probed for an exposed .git directory to download the site's source history and config	`GET /.git/HEAD`	declared bot	web
02:27	zmey.eu	requested an AWS credentials file left in a web-accessible path by mistake	`GET /.aws/credentials`	declared bot	web
02:27	zmey.eu	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
02:27	zmey.eu	5× requested a .env file, hoping to find API keys or database credentials (5 distinct paths)	`GET /core/.env`	declared bot	web
02:27	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /.env`	declared bot	edge
02:27	zmey.eu	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
02:27	zmey.eu	requested a private SSH key file by its conventional name	`GET /id_dsa`	declared bot	web
02:27	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /web/.env`	declared bot	web
02:27	zmey.eu	made a request that matched no known pattern	`GET /.config/gcloud/credentials.db`	declared bot	web
02:27	zmey.eu	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 /.config/gcloud/application_default_credentials.json`	declared bot	web
02:27	zmey.eu	requested a private SSH key file by its conventional name	`GET /.ssh/id_rsa`	declared bot	web
02:27	zmey.eu	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 /.ssh/config`	declared bot	web
02:27	zmey.eu	requested a private SSH key file by its conventional name	`GET /.ssh/id_ed25519`	declared bot	web
02:27	zmey.eu	5× requested a .env file, hoping to find API keys or database credentials (5 distinct paths)	`GET /server/.env`	declared bot	web
02:27	zmey.eu	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /media../.env`	declared bot	web
02:27	zmey.eu	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /.env.prod`	declared bot	web

Network

ASN: AS396982 Google LLC
Network type: cloud
Reverse DNS: 203.82.107.136.bc.googleusercontent.com
Country: United States US
Flags: cloud range (GCP)
Abuse contact: found in the registry
Checked: 18 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.