34.34.129.14

Blocked Persistent Regular Toolkit

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

Record

Score: 70/100each request counts half as much after 30 days
Worst level: Persistent
Attack-shaped requests: 46,125all time
Active days: 2UTC days
First seen: 23 Oct 2026
Last seen: 24 Oct 2026 07:55
Servers hit: 2
Targets: 2sites
Times blocked: 1by the evidence rules

First seen on 23 Oct 2026 13:26 UTC, most recently active on 24 Oct 2026 07:55 UTC.

Recorded 46,125 attack-shaped requests across 2 separate days.

Its traffic requested a .env file, hoping to find API keys or database credentials (24,159 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (6,981); 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 (3,738).

Seen by our edge and web sensors, against 2 of the sites we watch: haived.com and vaibed.com.

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

Its busiest hour on record began 24 Oct 2026 06:00 UTC, with 3,098 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 2 of the last 90 UTC days. Current block: 23 Oct 2026, with no end date.

Daily counts

Attack requests per UTC day, days with activity only
Day (UTC)	Requests
23 Oct 2026	24,687
24 Oct 2026	21,438

At least 261 requests a minute at its peak (24 Oct 2026 06:44 UTC; identical requests in the same second are stored once).
Methods: GET 46,187, POST 2,610.
The servers we watch answered: 403 46,563, 301 201 (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
24 Oct 2026
07:55	vaibed.com	7× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (7 distinct paths)	`POST /api/route`	declared bot	edge
07:55	haived.com	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
07:55	vaibed.com	3× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (3 distinct paths)	`POST /_next/server`	declared bot	edge
07:55	haived.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 /firebase-config.js`	declared bot	web
07:55	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /supabase/.env`	declared bot	web
07:55	haived.com	made a request that matched no known pattern	`GET /samconfig.toml`	declared bot	web
07:55	haived.com	requested a .env file, hoping to find API keys or database credentials	`GET /docker-compose/.env`	declared bot	web
07:55	haived.com	2× made a request that matched no known pattern (2 distinct paths)	`GET /terraform.tfstate.backup`	declared bot	web
07:55	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.dev.yml`	declared bot	web
07:55	haived.com	made a request that matched no known pattern	`GET /config/environment.json`	declared bot	web
07:55	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.prod.yml`	declared bot	web
07:55	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /application/.env`	declared bot	web
07:55	haived.com	requested docker-compose.yml, which often contains embedded passwords and connection strings	`GET /docker-compose.override.yml`	declared bot	web
07:55	haived.com	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 /.docker/secrets.json`	declared bot	web
07:55	haived.com	2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)	`GET /docker-compose.production.yml`	declared bot	web
07:55	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /config/.env.staging`	declared bot	web
07:55	haived.com	made a request that matched no known pattern	`GET /config/database.json`	declared bot	web
07:55	haived.com	10× requested a .env file, hoping to find API keys or database credentials (10 distinct paths)	`GET /config/env/aws_credentials.env`	declared bot	web
07:55	haived.com	probed for an exposed .svn directory to read the site's version-control metadata	`GET /.svn/entries`	declared bot	web
07:55	haived.com	requested a config.json file, hoping it exposes API keys or internal settings	`GET /.docker/config.json`	declared bot	web
07:55	haived.com	2× requested a private SSH key file by its conventional name (2 distinct paths)	`GET /id_dsa`	declared bot	web
07:55	haived.com	requested a .env file, hoping to find API keys or database credentials	`GET /etc/.env`	declared bot	web
07:55	haived.com	requested a private SSH key file by its conventional name	`GET /id_rsa`	declared bot	web
07:55	haived.com	2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)	`GET /env/.env`	declared bot	web

Network

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