34.146.26.35

Blocked Brute Toolkit

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

Record

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

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

Seen by our edge and web sensors, against 4emx.com.

Scored into the "Brute" level now; the highest it has reached is "Persistent". Badge: Toolkit.

Its busiest hour on record began UTC, with 141 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
141
  • At least 111 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 118, POST 13.
  • The servers we watch answered: 404 116, 403 22 (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
4emx.com2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)POST /cgi-bin/php?declared botweb
4emx.comfuzzed a short, random filename looking for a forgotten script that respondsPOST /index.php?declared botweb
4emx.com2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)POST /cgi-bin/php?declared botweb
4emx.comtried to abuse a local or remote file inclusion parameter such as allow_url_includePOST /php-cgi/php-cgi.exe?declared botweb
4emx.comfuzzed a short, random filename looking for a forgotten script that respondsPOST /index.php?declared botweb
4emx.comclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /api/templates/previewdeclared botweb
4emx.com2× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner/apinoneweb
4emx.com2× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (2 distinct paths)POST /admindeclared botedge
4emx.com5× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (5 distinct paths)GET /static../.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /static//.envdeclared botweb
4emx.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /_image?declared botweb
4emx.commade a request that matched no known patternGET /%2Fapi/configdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentials/.envnoneweb
4emx.com3× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (3 distinct paths)GET /api/orders/..%2fadmin/config.jsondeclared botweb
4emx.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /_nuxt/../.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentials/.envnoneweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
4emx.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /@fs/.env?declared botweb
4emx.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /@fs/proc/self/environ?declared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.local?declared botweb
4emx.com3× requested a .env file, hoping to find API keys or database credentials/.envnoneweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
4emx.com5× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.development?declared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.local?declared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
4emx.com2× used Vite dev server's @fs/ path to try to read arbitrary files outside the project root (2 distinct paths)GET /@fs/var/run/secrets/kubernetes.io/serviceaccount/ca.crt?declared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentials/.envnoneweb
4emx.com4× requested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
35.26.146.34.bc.googleusercontent.com
Country
Japan JP
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.