34.159.240.255

Blocked Persistent Toolkit

Blocked since 14 Oct 2026 13:22 UTC, no end date. Our servers refuse it, web requests included, and it is in feed.txt.

Record

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

First seen on 14 Oct 2026 13:16 UTC, most recently active on 14 Oct 2026 13:16 UTC.

Recorded 173 attack-shaped requests across 1 separate day.

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

Seen by our edge and web sensors, against victorantonov.com.

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

Its busiest hour on record began 14 Oct 2026 13:00 UTC, with 173 requests.

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

Surfaces: web-app. Attack types: known exploits, injection, scanning, hunting for secrets, unclassified. Seen by: edge, web.

Activity, last 90 days

Active on 1 of the last 90 UTC days. Current block: 14 Oct 2026, with no end date.

Daily counts

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

At least 173 requests a minute at its peak (14 Oct 2026 13:16 UTC; identical requests in the same second are stored once).
Methods: GET 176, POST 8.
The servers we watch answered: 404 105, 403 3, 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
14 Oct 2026
13:16	victorantonov.com	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)	`/cgi-bin/php-cgi`	none	web
13:16	victorantonov.com	was blocked at the edge without matching any specific attack signature	`GET /.env_1`	declared bot	edge
13:16	victorantonov.com	probed a WordPress admin/content path used to fingerprint the installation or hunt for an exposed upload/plugin surface	`GET /wp-admin/`	declared bot	edge
13:16	victorantonov.com	requested a .env file, hoping to find API keys or database credentials	`GET /services/.env`	declared bot	edge
13:16	victorantonov.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
13:16	victorantonov.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /index.php?`	declared bot	web
13:16	victorantonov.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
13:16	victorantonov.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
13:16	victorantonov.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yml`	declared bot	web
13:16	victorantonov.com	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
13:16	victorantonov.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /index.php?`	declared bot	web
13:16	victorantonov.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.yaml`	declared bot	web
13:16	victorantonov.com	made a request that matched no known pattern	`GET /%2Fapi/config`	declared bot	web
13:16	victorantonov.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/data/..%2f..%2f.env`	declared bot	web
13:16	victorantonov.com	requested a private SSH key file by its conventional name	`GET /id_rsa`	declared bot	web
13:16	victorantonov.com	21× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (21 distinct paths)	`/terraform.tfstate.backup`	none	web
13:16	victorantonov.com	probed for an exposed .svn directory to read the site's version-control metadata	`/.svn`	none	web
13:16	victorantonov.com	sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked	`/__vite_rsc_findSourceMapURL`	none	web

Network

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