136.69.228.51

Blocked Brute 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
372all time
Active days
1UTC days
First seen
Last seen
Servers hit
3
Targets
2sites
Times blocked
0by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 372 attack-shaped requests across 1 separate day.

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

Seen by our edge and web sensors, against 2 of the sites we watch: servbg.com and zmey.eu.

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

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

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

Surfaces: honeypot, web-app. Attack types: fake crawlers, 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
323
  • At least 274 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 339, POST 24.
  • The servers we watch answered: 403 189, 404 87, 200 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
zmey.eu2× was turned away at the edge because the address is already on our block list; not counted as new evidencePOST /form/declared botedge
zmey.euclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /exec-pydeclared botedge
zmey.eu2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)POST /webhook-test/declared botedge
zmey.eutried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute codePOST /cgi-bin/php-cgideclared botedge
zmey.eu3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)POST /api/designer/v1/file-contentdeclared botedge
zmey.eutried to abuse a local or remote file inclusion parameter such as allow_url_includePOST /index.phpdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidencePOST /api/v1/build_public_tmp/00000000-0000-0000-0000-000000000000/flowdeclared botedge
zmey.euclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /langflow/api/v1/validate/codedeclared botedge
zmey.eu2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)POST /dashboarddeclared botedge
zmey.eu3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /secrets.ymldeclared botedge
zmey.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.ymldeclared botedge
zmey.eu3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /gcp-credentials.jsondeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfiles/xdeclared botedge
zmey.eu5× was turned away at the edge because the address is already on our block list; not counted as new evidence (5 distinct paths)GET /service-account.jsondeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfilesdeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /app/.envdeclared botedge
zmey.eu3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /compose.ymldeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidencePOST /apideclared botedge
zmey.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.yamldeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /dist/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /gcp-service.jsondeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.productiondeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /serverless.yamldeclared botedge
zmey.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.production.ymldeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /supabase/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.docker/secrets.jsondeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /app/..;/.envdeclared botedge
zmey.eu2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)GET /uploads../.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.idea/WebServers.xmldeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /api/uploads/%2e%2e%2f%2e%2e%2f.envdeclared botedge
zmey.eurequested a private SSH key file by its conventional nameGET /id_ed25519declared botedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
51.228.69.136.bc.googleusercontent.com
Country
United States US
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.