136.70.191.162

Blocked Persistent Toolkit

Blocked since 17 Oct 2026 06:32 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: 220all time
Active days: 1UTC days
First seen: 17 Oct 2026
Last seen: 17 Oct 2026 06:24
Servers hit: 2
Targets: 1site
Times blocked: 0by the evidence rules

First seen on 17 Oct 2026 06:24 UTC, most recently active on 17 Oct 2026 06:24 UTC.

Recorded 220 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (135 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 triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (12).

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

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

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

Daily counts

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

At least 220 requests a minute at its peak (17 Oct 2026 06:24 UTC; identical requests in the same second are stored once).
Methods: GET 207, POST 13.
The servers we watch answered: 301 208 (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
06:24	haived.com	10× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (10 distinct paths)	`POST /api/route`	declared bot	edge
06:24	haived.com	4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)	`GET /client/.env`	declared bot	web
06:24	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.production.yml`	declared bot	web
06:24	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /deploy/.env`	declared bot	web
06:24	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.staging.yml`	declared bot	web
06:24	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /chatbot/.env`	declared bot	web
06:24	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.override.yml`	declared bot	web
06:24	haived.com	4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)	`GET /docker-compose/.env`	declared bot	web
06:24	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.prod.yml`	declared bot	web
06:24	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /infra/.env`	declared bot	web
06:24	haived.com	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
06:24	haived.com	4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)	`GET /.env.local?`	declared bot	web
06:24	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.dev.yml`	declared bot	web
06:24	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /.env?`	declared bot	web
06:24	haived.com	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
06:24	haived.com	claimed to be Bingbot while requesting an admin or credentials path the real crawler never touches	`GET /.env.local::$DATA?`	declared bot	web
06:24	haived.com	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
06:24	haived.com	3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)	`GET /@fs/.env?`	declared bot	web
06:24	haived.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
06:24	haived.com	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
06:24	haived.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
06:24	haived.com	requested a .env file, hoping to find API keys or database credentials	`GET /temp/.env`	declared bot	web
06:24	haived.com	requested a Vite/React-Server-Components source map, likely while mapping the app's bundled source	`GET /__vite_rsc_findSourceMapURL?`	declared bot	web
06:24	haived.com	used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root	`GET /_image?`	declared bot	web
06:24	haived.com	requested a .env file, hoping to find API keys or database credentials	`GET /application/.env.sample`	declared bot	web
06:24	haived.com	used Vite dev server's @fs/ path to try to read arbitrary files outside the project root	`GET /@fs/proc/self/cmdline?`	declared bot	web

Network

ASN: AS396982 Google LLC
Network type: cloud
Reverse DNS: 162.191.70.136.bc.googleusercontent.com
Country: United States US
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.