34.84.136.205

Blocked Brute Toolkit

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

Record

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

First seen on UTC, most recently active on UTC.

Recorded 372 attack-shaped requests across 1 separate day.

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

Seen by our web sensor, against 2 of the sites we watch: obdebug.com and odor-ex.com.

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

Its busiest hour on record began UTC, with 372 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
372
  • At least 202 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 327, POST 2.
  • The servers we watch answered: 403 204, 404 180 (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
odor-ex.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /js../.envdeclared botweb
odor-ex.com2× made a request that matched no known pattern (2 distinct paths)/odor-ex.com/.svnnoneweb
odor-ex.comrequested a .env file, hoping to find API keys or database credentialsGET /admin%2F.envdeclared botweb
odor-ex.comprobed for an exposed .svn directory to read the site's version-control metadataGET /.svn/entriesdeclared botweb
odor-ex.comrequested a .env file, hoping to find API keys or database credentialsGET /config/env/aws_credentials.envdeclared botweb
odor-ex.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /.docker/config.jsondeclared botweb
odor-ex.comrequested a .env file, hoping to find API keys or database credentialsGET /.github/.envdeclared botweb
odor-ex.com2× requested a private SSH key file by its conventional name (2 distinct paths)/odor-ex.com/id_dsanoneweb
odor-ex.comrequested a .env file, hoping to find API keys or database credentials/odor-ex.com/.env.wwwnoneweb
odor-ex.comrequested a private SSH key file by its conventional name/odor-ex.com/id_ed25519noneweb
odor-ex.commade a request that matched no known pattern/odor-ex.com/.gitconfignoneweb
odor-ex.com3× requested a private SSH key file by its conventional name (3 distinct paths)GET /.ssh/id_dsadeclared botweb
odor-ex.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.wwwdeclared botweb
odor-ex.comrequested a private SSH key file by its conventional nameGET /id_ed25519declared botweb
odor-ex.commade a request that matched no known patternGET /.gitconfigdeclared botweb
odor-ex.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)/odor-ex.com/.env.livenoneweb
odor-ex.com28× requested a .env file, hoping to find API keys or database credentials (28 distinct paths)GET /.env.livedeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
205.136.84.34.bc.googleusercontent.com
Country
Japan JP
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.