35.198.201.80

Blocked Persistent Toolkit

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

Record

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

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

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

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

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

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

Surfaces: 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
262
  • At least 210 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 251, POST 14.
  • The servers we watch answered: 404 237, 403 25 (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
schetio.com2× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (2 distinct paths)/icecoder/lib/file-control.phpnoneweb
schetio.comclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /lib/terminal-xhr.phpdeclared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentials/.envnoneweb
schetio.com6× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (6 distinct paths)POST /actionsdeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
schetio.com4× requested a .env file, hoping to find API keys or database credentials/.envnoneweb
schetio.com2× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (2 distinct paths)POST /api/routedeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.local?declared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /@fs/.env?declared botweb
schetio.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /@fs/proc/self/environ?declared botweb
schetio.com7× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /@fs/root/.env?declared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
schetio.com2× requested an AWS credentials file left in a web-accessible path by mistake (2 distinct paths)GET /@fs/root/.aws/credentials?declared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
schetio.com3× requested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
schetio.comused Vite dev server's @fs/ path to try to read arbitrary files outside the project rootGET /@fs/proc/self/cmdline?declared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /@fs/app/.env.local?declared botweb
schetio.comused Vite dev server's @fs/ path to try to read arbitrary files outside the project rootGET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?declared botweb
schetio.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
schetio.com6× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /@fs/.env?declared botweb
schetio.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ec2-user/.aws/credentials?declared botweb
schetio.comused Vite dev server's @fs/ path to try to read arbitrary files outside the project rootGET /@fs/var/run/secrets/kubernetes.io/serviceaccount/token?declared botweb
schetio.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/..%252f..%252f..%252f..%252f..%252fproc/self/environ?declared botweb
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /@fs/app/.env?declared botweb
schetio.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/../.env?declared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
80.201.198.35.bc.googleusercontent.com
Country
Singapore SG
Flags
cloud range (GCP)
Abuse contact
not found
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.