34.182.16.142

Blocked Persistent Toolkit

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

Record

Score
46/100each request counts half as much after 30 days
Worst level
Persistent
Attack-shaped requests
263all 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 263 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (134 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. Badge: Toolkit.

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

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

Surfaces: honeypot, web-app. Attack types: fake crawlers, 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
263
  • At least 263 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 183, 404 83, 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.comprobed for an exposed .svn directory to read the site's version-control metadata/.svnnoneweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.envdeclared botedge
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/../.envdeclared botedge
servbg.com10× requested a .env file, hoping to find API keys or database credentials (10 distinct paths)GET /model/.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.com6× requested a .env file, hoping to find API keys or database credentials (6 distinct paths)GET /chatbot/.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.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /_image?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.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /agents/.envdeclared botweb
servbg.comused Vite dev server's @fs/ path to try to read arbitrary files outside the project rootGET /@fs/var/run/secrets/kubernetes.io/serviceaccount/token?declared botweb
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /@fs/app/.env.production?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 config.json file, hoping it exposes API keys or internal settingsGET /.docker/config.jsondeclared botweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /services/.envdeclared botweb
servbg.comprobed for an exposed .svn directory to read the site's version-control metadataGET /.svn/entriesdeclared botweb
servbg.comclaimed to be Bingbot while requesting an admin or credentials path the real crawler never touchesGET /.env.development::$DATA?declared botweb
servbg.comused Vite dev server's @fs/ path to try to read arbitrary files outside the project rootGET /@fs/proc/self/cmdline?declared botweb
servbg.com2× requested a .env file, hoping to find API keys or database credentials/.env.developmentnoneweb
servbg.comrequested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated/confignoneweb
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.envdeclared botedge
servbg.comused Vite dev server's @fs/ path to try to read arbitrary files outside the project rootGET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?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.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /@fs/root/.env?declared botweb
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /api/data/..%2f..%2f.envdeclared botweb
servbg.com5× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.local?declared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
142.16.182.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.