34.65.172.242

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

First seen on UTC, most recently active on UTC.

Recorded 631 attack-shaped requests across 2 separate days.

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

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

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

Its busiest hour on record began UTC, with 434 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 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
572
59
  • At least 282 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 974, POST 18.
  • The servers we watch answered: 403 393, 404 60 (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)POST /api/authbrowser claimedge
servbg.com2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute codePOST /cgi-bin/phpdeclared botedge
servbg.comrequested wp-config.php or a backup copy of it, hoping to read the database password in clear textGET /wp-config.php.olddeclared botedge
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /api/console/api_serverdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.monorepodeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidencePOST /_nextbrowser claimedge
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 /.output/server/index.mjsdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /api/system/fileViewdeclared 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 /.output/nitro.jsondeclared botedge
servbg.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.swpdeclared botedge
servbg.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /api/console/api_serverdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /config/.env.phpdeclared botedge
servbg.comrequested wp-config.php or a backup copy of it, hoping to read the database password in clear textGET /wp-config.php.bakdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /production/.envdeclared botedge
servbg.com3× was turned away at the edge because the address is already on our block list; not counted as new evidence (3 distinct paths)GET /account/_payload.jsondeclared botedge
servbg.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /ses.envdeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.vercel/project.jsondeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.prod.bakdeclared botedge
servbg.com4× was turned away at the edge because the address is already on our block list; not counted as new evidence (4 distinct paths)GET /nuxt.config.tsdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /config.envdeclared botedge
servbg.comwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /next.config.jsdeclared botedge
servbg.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /packages/config/.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 /.bashrcdeclared botedge
servbg.comrequested a .env file, hoping to find API keys or database credentialsGET /server/.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 /.env.production.localdeclared botedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
242.172.65.34.bc.googleusercontent.com
Country
Switzerland CH
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.