34.180.71.224

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
259all 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 259 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (131 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 4emx.com.

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

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

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

Surfaces: honeypot, 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
259
  • At least 259 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 255, POST 14.
  • The servers we watch answered: 404 247, 200 5, 403 5 (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× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scannerPOST /apideclared botweb
4emx.com8× triggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attempt (8 distinct paths)POST /settingsdeclared botedge
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /config/env/aws_credentials.envdeclared botweb
4emx.comrequested a private SSH key file by its conventional nameGET /id_ed25519declared botweb
4emx.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.maildeclared botweb
4emx.comprobed for an exposed .svn directory to read the site's version-control metadata/.svnnoneweb
4emx.com2× requested a private SSH key file by its conventional name (2 distinct paths)GET /id_dsadeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.github/.envdeclared botweb
4emx.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /.docker/config.jsondeclared botweb
4emx.comprobed for an exposed .svn directory to read the site's version-control metadataGET /.svn/entriesdeclared botweb
4emx.comrequested a private SSH key file by its conventional nameGET /.ssh/id_dsadeclared botweb
4emx.commade a request that matched no known patternGET /.gitconfigdeclared botweb
4emx.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /backend/.envdeclared botweb
4emx.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.production.ymldeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /supabase/.envdeclared botweb
4emx.commade a request that matched no known patternGET /samconfig.tomldeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /admin/.envdeclared botweb
4emx.com3× requested docker-compose.yml, which often contains embedded passwords and connection strings (3 distinct paths)GET /docker-compose.staging.ymldeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /api/.envdeclared botweb
4emx.comrequested 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 webrootGET /credentials.jsondeclared botweb
4emx.comrequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.dev.ymldeclared botweb
4emx.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.olddeclared botweb
4emx.comclaimed to be Bingbot while requesting an admin or credentials path the real crawler never touchesGET /.env_1declared botweb
4emx.comrequested 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 webrootGET /.docker/secrets.jsondeclared botweb
4emx.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /application/.env.sampledeclared botweb
4emx.commade a request that matched no known patternGET /terraform.tfstate.backupdeclared botweb
4emx.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /application/.envdeclared botweb
4emx.comrequested 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 webrootGET /firebaseConfig.jsdeclared botweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.stagedeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
224.71.180.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.