35.242.253.35

Blocked Brute Toolkit

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

Record

Score
41/100each request counts half as much after 30 days
Worst level
Brute
Attack-shaped requests
173all time
Active days
1UTC days
First seen
Last seen
Servers hit
1
Targets
1site
Times blocked
0by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 173 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (109 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (37); it also requested a private SSH key file by its conventional name (6).

Seen by our web sensor, against haived.com.

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

Its busiest hour on record began UTC, with 173 requests.

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

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

Activity, last 90 days

Active on 1 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
173
  • At least 173 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 172, POST 1.
  • The servers we watch answered: 301 173 (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
haived.com6× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)GET /userfiles/x?declared botweb
haived.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /api/fs/read?declared botweb
haived.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /cache/original/%2e%2e/.envdeclared botweb
haived.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /api/system/fileView?declared botweb
haived.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /cache/original/%2e%2e/%2e%2e/.envdeclared botweb
haived.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /api/fs/read?declared botweb
haived.com7× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (6 distinct paths)GET /api/w/default/jobs_u/get_log_file/../../../../proc/self/environdeclared botweb
haived.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /settings%2F.envdeclared botweb
haived.comprobed for an exposed .git directory to download the site's source history and configGET /.git/HEADdeclared botweb
haived.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /web/.envdeclared botweb
haived.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialsdeclared botweb
haived.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /frontend/.envdeclared botweb
haived.comprobed for an exposed .git directory to download the site's source history and configGET /.git/configdeclared botweb
haived.com19× requested a .env file, hoping to find API keys or database credentials (19 distinct paths)GET /public/.envdeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
35.253.242.35.bc.googleusercontent.com
Country
Germany DE
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.