34.34.159.106

Blocked Brute Night Owl 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
223all 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 223 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (123 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 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 (15).

Seen by our web sensor, against servbg.com.

Scored into the "Brute" level, its highest so far. Badges: Night Owl and Toolkit.

Its busiest hour on record began UTC, with 223 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
223
  • At least 223 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 202, POST 1.
  • The servers we watch answered: 403 161, 404 64 (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
servbg.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.ymldeclared botweb
servbg.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /.docker/config.jsondeclared botweb
servbg.com2× requested a private SSH key file by its conventional name (2 distinct paths)GET /.ssh/id_rsadeclared botweb
servbg.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswddeclared botweb
servbg.comrequested 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 webrootGET /.ssh/configdeclared botweb
servbg.comrequested the .git directory itself, hoping it is exposed and browsable/.gitnoneweb
servbg.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.yamldeclared botweb
servbg.comrequested 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 webrootGET /credentials.jsondeclared botweb
servbg.comprobed for an exposed .git directory to download the site's source history and configGET /.git/HEADdeclared botweb
servbg.com2× 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 /secrets.jsondeclared botweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /secrets.envdeclared botweb
servbg.comrequested the .git directory itself, hoping it is exposed and browsable/.gitnoneweb
servbg.comrequested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated/confignoneweb
servbg.comrequested 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 webrootGET /.git-credentialsdeclared botweb
servbg.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialsdeclared botweb
servbg.comrequested 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 webrootGET /.aws/configdeclared botweb
servbg.comprobed for an exposed .git directory to download the site's source history and configGET /.git/configdeclared botweb
servbg.com23× requested a .env file, hoping to find API keys or database credentials (23 distinct paths)GET /core/.envdeclared botweb
servbg.com2× requested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated/confignoneweb
servbg.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 /push_config.jsondeclared botweb
servbg.comrequested 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 webrootGET /config/gcp-credentials.jsondeclared botweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.envdeclared botweb
servbg.comrequested 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 webrootGET /firebase-credentials.jsondeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
106.159.34.34.bc.googleusercontent.com
Country
Belgium BE
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.