34.19.210.25

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

First seen on UTC, most recently active on UTC.

Recorded 261 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (136 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 (17).

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

Scored into the "Persistent" level, its highest so far. Badge: Toolkit.

Its busiest hour on record began UTC, with 261 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
261
  • At least 261 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 333, POST 11.
  • The servers we watch answered: 403 183, 404 81, 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
neutralizatori.com6× was turned away at the edge because the address is already on our block list; not counted as new evidence (5 distinct paths)POST /appdeclared botedge
neutralizatori.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ubuntu/.aws/credentialsdeclared botedge
neutralizatori.com2× 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.development.localdeclared botedge
neutralizatori.comclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /actionsdeclared botedge
neutralizatori.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ec2-user/.aws/credentialsdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /railway.jsondeclared botedge
neutralizatori.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfilesdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.cargo/credentials.tomldeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /@fs/proc/self/cwd/.envdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidencePOST /api/routedeclared botedge
neutralizatori.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.dev.ymldeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.dockercfgdeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /docker/.envdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.env.staging.localdeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /frontend/.envdeclared botedge
neutralizatori.comprobed for an exposed .git directory to download the site's source history and configGET /.git/configdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.dev.vars.productiondeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /.next/.envdeclared botedge
neutralizatori.com2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)GET /.dockerenvdeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /prisma/.envdeclared botedge
neutralizatori.com2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)GET /compose.yamldeclared botedge
neutralizatori.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.production.ymldeclared botedge
neutralizatori.comrequested a private SSH key file by its conventional nameGET /.ssh/id_rsadeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /credentials.jsondeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /config/.env.productiondeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /service_account.jsondeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /settings%2F.envdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /serviceAccountKey.jsondeclared botedge
neutralizatori.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /app/..;/.envdeclared botedge
neutralizatori.comrequested a private SSH key file by its conventional nameGET /.ssh/id_ed25519declared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.gitlab-ci.ymldeclared botedge
neutralizatori.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.override.ymldeclared botedge
neutralizatori.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /web/.envdeclared botedge
neutralizatori.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /....//....//....//..../.envdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /terraform.tfvarsdeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.olddeclared botedge
neutralizatori.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.staging.ymldeclared botedge
neutralizatori.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /dist../.envdeclared botedge
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /config/.envdeclared botedge
neutralizatori.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /backofficebrowser claimedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
25.210.19.34.bc.googleusercontent.com
Country
Canada CA
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.