34.74.102.237
Blocked Persistent Regular Toolkit
Blocked since UTC, no end date. Our servers refuse it, web requests included, and it is in feed.txt.
Record
- Score
- 53/100each request counts half as much after 30 days
- Worst level
- Persistent
- Attack-shaped requests
- 492all time
- Active days
- 3UTC days
- First seen
- Last seen
- Servers hit
- 3
- Targets
- 2sites
- Times blocked
- 1by the evidence rules
First seen on UTC, most recently active on UTC.
Recorded 492 attack-shaped requests across 3 separate days.
Its traffic requested a .env file, hoping to find API keys or database credentials (326 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (65); 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 (30).
Seen by our edge and web sensors, against 2 of the sites we watch: servbg.com and zmey.eu.
Scored into the "Persistent" level, its highest so far. Badges: Regular and Toolkit.
Its busiest hour on record began UTC, with 249 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 3 of the last 90 UTC days. Current block: , with no end date.
Daily counts
| Day (UTC) | Requests |
|---|---|
| 249 | |
| 214 | |
| 43 |
- At least 249 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
- Methods: GET 713, POST 4.
- The servers we watch answered: 404 251, 403 8, 200 5 (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.
| Time | Site | What happened | Request | User agent | Seen by |
|---|---|---|---|---|---|
| servbg.com | 3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths) | GET /env.old | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /.env.production.bak | declared bot | edge | |
| servbg.com | 2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths) | GET /.env.production.local | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /dev/.env | declared bot | edge | |
| servbg.com | was turned away at the edge because the address is already on our block list; not counted as new evidence | GET /.firebaserc | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /v2/.env | declared bot | edge | |
| servbg.com | 3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths) | GET /next.config.mjs | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /server/.env | declared bot | edge | |
| servbg.com | 2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths) | GET /service_account.json | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /frontend/.env | declared bot | edge | |
| servbg.com | 3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths) | GET /var/run/secrets/kubernetes.io/serviceaccount/token | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /app/.env | declared bot | edge | |
| servbg.com | 2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths) | GET /vercel.json | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /build/.env | declared bot | edge | |
| servbg.com | was turned away at the edge because the address is already on our block list; not counted as new evidence | GET /.turbo/config.json | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /.env.staging | declared bot | edge | |
| servbg.com | 7× was turned away at the edge because the address is already on our block list; not counted as new evidence (7 distinct paths) | GET /secrets.yml | declared bot | edge | |
| servbg.com | 3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths) | GET /core/.env | declared bot | edge | |
| servbg.com | was turned away at the edge because the address is already on our block list; not counted as new evidence | GET /.env%3F.css | declared bot | edge | |
| servbg.com | 3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths) | GET /config/.env.staging | declared bot | edge | |
| servbg.com | 2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths) | GET /gcp-service.json | declared bot | edge | |
| servbg.com | requested a .env file, hoping to find API keys or database credentials | GET /.env.old | declared bot | edge | |
| servbg.com | used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root | GET /js../.env | declared bot | edge | |
| servbg.com | 3× requested a .env file, hoping to find API keys or database credentials (2 distinct paths) | GET /.env | declared bot | edge | |
| servbg.com | 4× was turned away at the edge because the address is already on our block list; not counted as new evidence (4 distinct paths) | GET /.dev.vars.staging | declared bot | edge | |
Network
- ASN
- AS396982 Google LLC
- Network type
- cloud
- Reverse DNS
237.102.74.34.bc.googleusercontent.com- Country
- United States US
- Flags
- cloud range (GCP)
- Abuse contact
- found in the registry
- Checked
Your verdict
What readers make of this address. Verdicts are opinions of signed-in Academy members. They never change blocking or reporting.
Sign in with your free Academy account to cast a verdict. Sign in
No verdicts yet.