34.141.99.119

Blocked Brute Toolkit

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

Record

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

First seen on 12 Oct 2026 13:49 UTC, most recently active on 12 Oct 2026 13:49 UTC.

Recorded 265 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (142 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 neutralizatori.com.

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

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

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

Surfaces: 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: 12 Oct 2026, with no end date.

Daily counts

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

At least 265 requests a minute at its peak (12 Oct 2026 13:49 UTC; identical requests in the same second are stored once).
Methods: GET 252, POST 15.
The servers we watch answered: 404 238, 403 30, 301 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
12 Oct 2026
13:49	neutralizatori.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:49	neutralizatori.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /index.php?`	declared bot	web
13:49	neutralizatori.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:49	neutralizatori.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:49	neutralizatori.com	tried to abuse a local or remote file inclusion parameter such as allow_url_include	`POST /index.php?`	declared bot	web
13:49	neutralizatori.com	claimed to be Googlebot while POSTing, something the real crawler never does	`POST /api/templates/preview`	declared bot	web
13:49	neutralizatori.com	3× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (3 distinct paths)	`POST /api/auth`	declared bot	edge
13:49	neutralizatori.com	made a request that matched no known pattern	`GET /config/environment.json`	declared bot	web
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`/.env`	none	web
13:49	neutralizatori.com	triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt	`POST /api`	declared bot	edge
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/app/.env.production?`	declared bot	web
13:49	neutralizatori.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?`	declared bot	web
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/src/.env?`	declared bot	web
13:49	neutralizatori.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /@fs/../.env?`	declared bot	web
13:49	neutralizatori.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/token?`	declared bot	web
13:49	neutralizatori.com	requested an AWS credentials file left in a web-accessible path by mistake	`GET /@fs/home/ec2-user/.aws/credentials?`	declared bot	web
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/.env?`	declared bot	web
13:49	neutralizatori.com	2× requested an AWS credentials file left in a web-accessible path by mistake (2 distinct paths)	`GET /@fs/root/.aws/credentials?`	declared bot	web
13:49	neutralizatori.com	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
13:49	neutralizatori.com	6× requested a .env file, hoping to find API keys or database credentials (5 distinct paths)	`GET /@fs/app/.env?`	declared bot	web
13:49	neutralizatori.com	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
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`GET /@fs/src/.env?`	declared bot	web
13:49	neutralizatori.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /@fs/../.env?`	declared bot	web
13:49	neutralizatori.com	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /@fs/app/.env?`	declared bot	web
13:49	neutralizatori.com	2× made a request that matched no known pattern (2 distinct paths)	`GET /.cargo/credentials.toml`	declared bot	web
13:49	neutralizatori.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 /.config/gcloud/application_default_credentials.json`	declared bot	web
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`GET /.env.preprod`	declared bot	web
13:49	neutralizatori.com	made a request that matched no known pattern	`GET /.config/gcloud/credentials.db`	declared bot	web
13:49	neutralizatori.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /.env.keys`	declared bot	web
13:49	neutralizatori.com	requested a private SSH key file by its conventional name	`GET /.ssh/id_ed25519`	declared bot	web
13:49	neutralizatori.com	requested a .env file, hoping to find API keys or database credentials	`GET /.env.secret`	declared bot	web
13:49	neutralizatori.com	requested .htaccess or .htpasswd, which can leak access rules or password hashes	`GET /.htpasswd`	declared bot	web
13:49	neutralizatori.com	made a request that matched no known pattern	`GET /supabase/config.toml`	declared bot	web
13:49	neutralizatori.com	2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)	`GET /docker-compose.yaml`	declared bot	web

Network

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