34.172.9.102

Blocked Persistent Night Owl Toolkit

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

Record

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

First seen on UTC, most recently active on UTC.

Recorded 268 attack-shaped requests across 1 separate day.

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

Seen by our edge and web sensors, against servbg.com.

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

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

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

Surfaces: honeypot, web-app. Attack types: injection, scanning, hunting for secrets. Seen by: edge, 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
268
  • At least 268 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 259, POST 1.
  • The servers we watch answered: 403 186, 404 85, 200 6 (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.com6× requested a .env file, hoping to find API keys or database credentials (6 distinct paths)GET /agents/.envdeclared botweb
servbg.commade a request that matched no known patternGET /.dbeaver/credentials-config.jsondeclared botweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.credentialsdeclared botweb
servbg.commade a request that matched no known patternGET /.cargo/credentials.tomldeclared botweb
servbg.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /.env.configdeclared botweb
servbg.com7× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)/.env.productionnoneweb
servbg.com3× requested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated/confignoneweb
servbg.com3× requested a .env file, hoping to find API keys or database credentialsGET /.envdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /workspace/.envdeclared botweb
servbg.commade a request that matched no known patternGET /supabase/config.tomldeclared botweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /project/.envdeclared botweb
servbg.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /api/v1/.envdeclared botweb
servbg.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswddeclared botweb
servbg.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
servbg.commade a request that matched no known patternGET /%2Fapi/configdeclared botweb
servbg.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared 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/gcloud/application_default_credentials.jsondeclared botweb
servbg.commade a request that matched no known patternGET /.config/gcloud/credentials.dbdeclared 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 a .env file, hoping to find API keys or database credentialsGET /.env.production?declared botweb
servbg.comrequested a private SSH key file by its conventional nameGET /.ssh/id_ed25519declared botweb
servbg.com2× requested a .env file, hoping to find API keys or database credentialsGET /.env.development?declared botweb
servbg.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
servbg.comrequested a private SSH key file by its conventional nameGET /.ssh/id_rsadeclared botweb
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.local?declared botweb
servbg.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /@fs/proc/self/environ?declared botweb
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /@fs/root/.env?declared botweb
servbg.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.override.ymldeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
102.9.172.34.bc.googleusercontent.com
Country
United States US
Flags
cloud range (GCP)
Abuse contact
not found
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.