34.13.153.188

Blocked Persistent 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
265all time
Active days
1UTC days
First seen
Last seen
Servers hit
2
Targets
1site
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 265 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (149 requests); it also used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (36); 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 stefanpetkov.day.

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

Its busiest hour on record began UTC, with 265 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
265
  • At least 265 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 249, POST 13.
  • The servers we watch answered: 404 233, 403 35 (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.day3× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner (3 distinct paths)GET /signinbrowser claimweb
stefanpetkov.dayprobed a Next.js/Auth.js (NextAuth) authentication route, consistent with fingerprinting a Next.js app's auth stackGET /authbrowser claimweb
stefanpetkov.day4× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner (4 distinct paths)GET /dashboardbrowser claimweb
stefanpetkov.dayprobed a Next.js/Auth.js (NextAuth) authentication route, consistent with fingerprinting a Next.js app's auth stackGET /auth/loginbrowser claimweb
stefanpetkov.daymade a request that matched no known patternGET /admin/usersbrowser claimweb
stefanpetkov.day3× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner (3 distinct paths)GET /signupbrowser claimweb
stefanpetkov.dayprobed a list of common site paths looking for an unprotected admin panel or staging copyGET /adminbrowser claimweb
stefanpetkov.day31× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (31 distinct paths)/icecoder/lib/file-control.phpnoneweb
stefanpetkov.daymade a request that matched no known pattern/stefanpetkovday/.svnnoneweb
stefanpetkov.day4× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (4 distinct paths)/.github/.envnoneweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
188.153.13.34.bc.googleusercontent.com
Country
The Netherlands NL
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.