34.179.195.143

Blocked Brute Toolkit

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

Record

Score
44/100each request counts half as much after 30 days
Worst level
Brute
Attack-shaped requests
428all time
Active days
1UTC days
First seen
Last seen
Servers hit
1
Targets
1site
Times blocked
0by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 428 attack-shaped requests across 1 separate day.

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

Seen by our web sensor, against 4emx.com.

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

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

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

Surfaces: web-app. Attack types: fake crawlers, injection, scanning, hunting for secrets. Seen by: 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
428
  • At least 215 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 405, POST 2.
  • The servers we watch answered: 404 377, 403 55 (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.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 /admin%2F.envdeclared botweb
4emx.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /api/uploads/%2e%2e%2f%2e%2e%2f.envdeclared botweb
4emx.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /settings%2F.envdeclared 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 /api%2F.envdeclared botweb
4emx.com3× requested a .env file, hoping to find API keys or database credentials/.envnoneweb
4emx.comprobed for an exposed .svn directory to read the site's version-control metadata/.svnnoneweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /static//.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET //.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /static//app/.envdeclared botweb
4emx.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /public../.envdeclared botweb
4emx.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /static//home/user/.envdeclared botweb
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 /js../.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.//.envdeclared botweb
4emx.com2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)GET /build../.envdeclared botweb
4emx.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /.docker/config.jsondeclared botweb
4emx.com2× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (2 distinct paths)GET /media../.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.github/.envdeclared botweb
4emx.com4× used a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web root (4 distinct paths)GET /uploads../.envdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /config/env/aws_credentials.envdeclared botweb
4emx.comprobed for an exposed .svn directory to read the site's version-control metadataGET /.svn/entriesdeclared botweb
4emx.com3× requested a private SSH key file by its conventional name (3 distinct paths)GET /id_dsadeclared botweb
4emx.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /tmp/.envdeclared botweb
4emx.commade a request that matched no known patternGET /.gitconfigdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /temp/.envdeclared botweb
4emx.comrequested a private SSH key file by its conventional nameGET /.ssh/id_dsadeclared botweb
4emx.com7× requested a .env file, hoping to find API keys or database credentials (7 distinct paths)GET /private/.envdeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
143.195.179.34.bc.googleusercontent.com
Country
Germany DE
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.