185.8.106.123

Blocked Scanner Toolkit

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

Record

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

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

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

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

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

Routed via AS204770 (UAB Cherry Servers), a hosting network.

Surfaces: web-app. Attack types: known exploits, 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
142
  • At least 59 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 164, POST 6.
  • The servers we watch answered: 404 117, 403 71 (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× requested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated/confignoneweb
4emx.commade a request that matched no known patternGET /config/runtime-env.jsbrowser claimweb
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 /env-config.jsbrowser claimweb
4emx.commade a request that matched no known patternGET /config/env.jsbrowser claimweb
4emx.comswept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner/apinoneweb
4emx.com3× requested a config.json file, hoping it exposes API keys or internal settings (3 distinct paths)GET /api/config.jsonbrowser claimweb
4emx.commade a request that matched no known pattern/.confignoneweb
4emx.comrequested a config.json file, hoping it exposes API keys or internal settingsGET /config.jsonbrowser claimweb
4emx.com3× made a request that matched no known pattern (3 distinct paths)GET /claude_desktop_config.jsonbrowser claimweb
4emx.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /proc/self/environbrowser claimweb
4emx.com2× requested a generic /config or /api/config endpoint, hoping the app exposes its runtime configuration unauthenticated/confignoneweb
4emx.commade a request that matched no known patternGET /config/secrets/aws.jsonbrowser claimweb
4emx.com4× requested an AWS credentials file left in a web-accessible path by mistake (4 distinct paths)GET /home/ec2-user/.aws/credentialsbrowser claimweb
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 /aws.ymlbrowser claimweb
4emx.com2× requested an AWS credentials file left in a web-accessible path by mistake (2 distinct paths)GET /backend/.aws/credentialsbrowser claimweb
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 /aws/credentialsbrowser claimweb
4emx.com3× probed a list of common site paths looking for an unprotected admin panel or staging copy (3 distinct paths)/backupnoneweb
4emx.comrequested a .env file, hoping to find API keys or database credentials/.envnoneweb
4emx.comprobed a list of common site paths looking for an unprotected admin panel or staging copy/oldnoneweb
4emx.comswept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner/dashboardnoneweb
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 /%2f.env.localbrowser claimweb
4emx.comrequested a .env file, hoping to find API keys or database credentialsGET /backup/.envbrowser claimweb
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 /.aws/configbrowser claimweb
4emx.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /%2f.envbrowser claimweb
4emx.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialsbrowser claimweb
4emx.com10× requested a .env file, hoping to find API keys or database credentials (10 distinct paths)GET /staging/.envbrowser claimweb
4emx.comswept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner/apinoneweb

Network

ASN
AS204770 UAB Cherry Servers
Network type
hosting
Reverse DNS
ip-185-8-106-123.008.ptr.cherryservers.net
Country
United States US
Flags
none observed
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.