34.159.221.79

Blocked Persistent Toolkit

Blocked since 17 Oct 2026 16:57 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: 89all time
Active days: 1UTC days
First seen: 17 Oct 2026
Last seen: 17 Oct 2026 08:48
Servers hit: 2
Targets: 1site
Times blocked: 1by the evidence rules

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

Recorded 89 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 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); it also requested the .git directory itself, hoping it is exposed and browsable (4).

Seen by our edge and web sensors, against zmey.eu.

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

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

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

Surfaces: honeypot, web-app. Attack types: 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	89

At least 89 requests a minute at its peak (17 Oct 2026 08:48 UTC; identical requests in the same second are stored once).
Methods: GET 87.
The servers we watch answered: 404 81, 403 6, 200 2 (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
08:48	zmey.eu	7× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (7 distinct paths)	`/.env.r2`	none	web
08:48	zmey.eu	3× requested the .git directory itself, hoping it is exposed and browsable	`/.git`	none	web
08:48	zmey.eu	10× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (10 distinct paths)	`/.env.php`	none	web
08:48	zmey.eu	requested wp-config.php or a backup copy of it, hoping to read the database password in clear text	`GET /wp-config.php.bak`	browser claim	edge
08:48	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /.env.r2`	browser claim	web
08:48	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 /runtime-config.js`	browser claim	web
08:48	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /.env.gcs`	browser claim	web
08:48	zmey.eu	made a request that matched no known pattern	`GET /config/keys/private.pem`	browser claim	web
08:48	zmey.eu	requested WordPress's debug.log, which can leak paths, queries or credentials left in debug output	`GET /wp-content/debug.log`	browser claim	web
08:48	zmey.eu	5× requested a .env file, hoping to find API keys or database credentials (5 distinct paths)	`GET /web/.env`	browser claim	web
08:48	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 /env-config.js`	browser claim	web
08:48	zmey.eu	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /src/.env`	browser claim	web
08:48	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 /secrets.json`	browser claim	web
08:48	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /server/.env`	browser claim	web
08:48	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/config.js`	browser claim	web
08:48	zmey.eu	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /public/.env`	browser claim	web
08:48	zmey.eu	requested phpinfo.php, which dumps the full PHP configuration and environment if left in place	`GET /phpinfo.php`	browser claim	web
08:48	zmey.eu	4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)	`GET /old/.env`	browser claim	web
08:48	zmey.eu	fuzzed a short, random filename looking for a forgotten script that responds	`GET /info.php`	browser claim	web
08:48	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.js`	browser claim	web
08:48	zmey.eu	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /frontend/.env`	browser claim	web
08:48	zmey.eu	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yml`	browser claim	web
08:48	zmey.eu	requested a .env file, hoping to find API keys or database credentials	`GET /demo/.env`	browser claim	web

Network

ASN: AS396982 Google LLC
Network type: cloud
Reverse DNS: 79.221.159.34.bc.googleusercontent.com
Country: Germany DE
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.