35.199.113.134

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
46/100each request counts half as much after 30 days
Worst level
Persistent
Attack-shaped requests
118all time
Active days
2UTC days
First seen
Last seen
Servers hit
1
Targets
1site
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 118 attack-shaped requests across 2 separate days.

Its traffic requested a .env file, hoping to find API keys or database credentials (80 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (11); it also requested a decoy path that only a scanner would ask for (6).

Seen by our edge and web sensors, against servbg.com.

Scored into the "Persistent" level, its highest so far. Badges: Regular and Toolkit.

Its busiest hour on record began UTC, with 56 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 2 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
62
56
  • At least 56 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 240.
  • The servers we watch answered: 200 4, 404 2 (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.com6× was turned away at the edge because the address is already on our block list; not counted as new evidence (6 distinct paths)GET /service-account.jsondeclared botedge
servbg.comrequested wp-config.php or a backup copy of it, hoping to read the database password in clear textGET /wp-config.olddeclared botedge
servbg.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 /secrets.ymldeclared botedge
servbg.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /web/.envdeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /google-services.jsondeclared botedge
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.backupdeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.aws/configdeclared botedge
servbg.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialsdeclared botedge
servbg.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /build/.envdeclared botedge
servbg.com5× was turned away at the edge because the address is already on our block list; not counted as new evidence (5 distinct paths)GET /push_config.jsondeclared botedge
servbg.comrequested the .git directory itself, hoping it is exposed and browsableGET /.git/config%3F.cssdeclared botedge
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /laravel../.envdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /dashboard%2F.envdeclared botedge
servbg.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 /firebase-admin.jsondeclared botedge
servbg.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.override.ymldeclared botedge
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /static../.envdeclared botedge
servbg.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 /terraform.tfstate.backupdeclared botedge
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /img../.envdeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /firebaseConfig.jsdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /application/.env.sampledeclared botedge
servbg.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.dev.ymldeclared botedge
servbg.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 /.s3cfgdeclared botedge
servbg.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.sendgriddeclared botedge
servbg.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 /serverless.yamldeclared botedge
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /temp/.envdeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.env_sampledeclared botedge
servbg.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /etc/.envdeclared botedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
134.113.199.35.bc.googleusercontent.com
Country
Brazil BR
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.