34.47.62.131

Blocked Persistent Regular Toolkit

Blocked since UTC, no end date. Our servers refuse it, web requests included, and it is in feed.txt.

Record

Score
62/100each request counts half as much after 30 days
Worst level
Persistent
Attack-shaped requests
13,787all time
Active days
3UTC days
First seen
Last seen
Servers hit
2
Targets
2sites
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 13,787 attack-shaped requests across 3 separate days.

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

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 UTC, with 1,507 requests.

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

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

Activity, last 90 days

Active on 3 of the last 90 UTC days. Current block: , with no end date.

Daily counts
Attack requests per UTC day, days with activity only
Day (UTC)Requests
2,240
9,289
2,258
  • At least 503 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 13,806, POST 807.
  • The servers we watch answered: 403 13,720, 404 249, 302 1 (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
TimeSiteWhat happenedRequestUser agentSeen by
vaibed.com6× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (6 distinct paths)POST /api/authbrowser claimedge
haived.comswept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scannerPOST /apibrowser claimweb
haived.com6× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /@fs/.env?declared botweb
haived.comswept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scannerPOST /apibrowser claimweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /api/.envdeclared botweb
haived.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ubuntu/.aws/credentials?declared botweb
haived.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/..%252f..%252f..%252f..%252f..%252fproc/self/environ?declared botweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.olddeclared botweb
haived.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/..%252f..%252f..%252f..%252f..%252froot/.env?declared botweb
haived.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.savedeclared botweb
haived.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/root/.aws/credentials?declared botweb
haived.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.proddeclared botweb
haived.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ec2-user/.aws/credentials?declared botweb
haived.com5× requested a .env file, hoping to find API keys or database credentials (5 distinct paths)GET /.env.backupdeclared botweb
haived.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /.changeset/config.jsondeclared botweb
haived.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.localdeclared botweb
haived.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /.turbo/config.jsondeclared botweb
haived.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswddeclared botweb
haived.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /.env.keysdeclared botweb
haived.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.yamldeclared botweb
haived.commade a request that matched no known patternGET /supabase/config.tomldeclared botweb
haived.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/../.env?declared botweb
haived.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.ymldeclared botweb
haived.comrequested a .env file, hoping to find API keys or database credentialsGET /secrets.envdeclared botweb
haived.comprobed for an exposed .git directory to download the site's source history and configGET /.git/HEADdeclared botweb
haived.com3× 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 distinct paths)GET /secrets.ymldeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
131.62.47.34.bc.googleusercontent.com
Country
Canada CA
Flags
cloud range (GCP)
Abuse contact
found in the registry
Checked

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.

Every listing carries its evidence on its page, and blocks are lifted only by us; if you were blocked and have fixed the cause, write to abuse-reports@abuse.servbg.com.