34.21.207.175

Blocked Brute Toolkit

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

Record

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

Its traffic requested a .env file, hoping to find API keys or database credentials (31 requests); 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 (13); it also triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (6).

Seen by our edge and web sensors, against stefanpetkov.day.

Scored into the "Brute" level now; the highest it has reached is "Persistent". Badge: Toolkit.

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

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

Surfaces: web-app. Attack types: known exploits, 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
67
  • At least 66 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 56, POST 8.
  • The servers we watch answered: 404 54, 403 9 (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
stefanpetkov.dayfuzzed a short, random filename looking for a forgotten script that respondsPOST /index.php?declared botweb
stefanpetkov.day3× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (3 distinct paths)POST /dashboarddeclared botedge
stefanpetkov.dayrequested a .env file, hoping to find API keys or database credentials/stefanpetkovday/.envnoneweb
stefanpetkov.dayrequested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticatedGET /api/configdeclared botweb
stefanpetkov.dayrequested a config.json file, hoping it exposes API keys or internal settingsGET /config.jsondeclared botweb
stefanpetkov.dayrequested 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.jsdeclared botweb
stefanpetkov.dayprobed a WordPress admin/content path used to fingerprint the installation or hunt for an exposed upload/plugin surfaceGET /wp-jsondeclared botweb
stefanpetkov.day2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfiles?declared botweb
stefanpetkov.day2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /api/fs/read?declared botweb
stefanpetkov.dayused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /cache/original/%2e%2e/.envdeclared botweb
stefanpetkov.day2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /api/.env/public/.envdeclared botweb
stefanpetkov.dayrequested 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
stefanpetkov.day2× requested a private SSH key file by its conventional name (2 distinct paths)GET /.ssh/id_ed25519declared botweb
stefanpetkov.dayrequested .htaccess or .htpasswd, which can leak access rules or password hashes/stefanpetkovday/.htpasswdnoneweb
stefanpetkov.dayrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswddeclared botweb
stefanpetkov.day2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)GET /docker-compose.yamldeclared botweb
stefanpetkov.day2× 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 /.git-credentialsdeclared botweb
stefanpetkov.dayrequested a .env file, hoping to find API keys or database credentialsGET /secrets.envdeclared botweb
stefanpetkov.day2× 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
stefanpetkov.day2× made a request that matched no known pattern/stefanpetkovday/.gitnoneweb
stefanpetkov.dayrequested 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
stefanpetkov.dayrequested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialsdeclared botweb
stefanpetkov.day2× probed for an exposed .git directory to download the site's source history and config (2 distinct paths)GET /.git/HEADdeclared botweb
stefanpetkov.day16× requested a .env file, hoping to find API keys or database credentials (16 distinct paths)GET /core/.envdeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
175.207.21.34.bc.googleusercontent.com
Country
Singapore SG
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.