194.180.49.41

Blocked Wanted Regular Toolkit

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

Record

Score
58/100each request counts half as much after 30 days
Worst level
Wanted
Attack-shaped requests
903all time
Active days
13UTC days
First seen
Last seen
Servers hit
11
Targets
15sites
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 903 attack-shaped requests across 13 separate days.

Its traffic requested a .env file, hoping to find API keys or database credentials (384 requests); it also requested a decoy path that only a scanner would ask for (379); it also requested wp-config.php or a backup copy of it, hoping to read the database password in clear text (62).

Seen by our edge, honeypot and web sensors, against 15 of the sites we watch, among them 4emx.com, amosix.eu, bgpoet.com, carrentvarna.com and dubstard.com.

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

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

Routed via AS201814 (MEVSPACE sp. z o.o.), a home broadband network.

Surfaces: honeypot, web-app. Attack types: leaked-password reuse, known exploits, scanning, hunting for secrets. Seen by: edge, honeypot, web.

Activity, last 90 days

Active on 13 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
13
35
13
69
15
23
86
78
3
1
20
530
17
  • At least 389 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 1,026, HEAD 1, POST 1.
  • The servers we watch answered: 429 465, 404 282, 200 68, 403 26 (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
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 webrootGET /application.propertieshoneypot
requested a decoy path that only a scanner would ask forGET /database.ymlhoneypot
2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)GET /docker-compose.yamlhoneypot
requested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialshoneypot
2× requested a decoy path that only a scanner would ask for (2 distinct paths)GET /appsettings.Production.jsonhoneypot
requested a config.json file, hoping it exposes API keys or internal settingsGET /config.jsonhoneypot
requested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswdhoneypot
fuzzed a short, random filename looking for a forgotten script that respondsGET /config.phphoneypot
2× requested wp-config.php or a backup copy of it, hoping to read the database password in clear text (2 distinct paths)GET /wp-config.php.bakhoneypot
3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.localhoneypot
requested a .env file, hoping to find API keys or database credentialsGET /.envhoneypot
requested a decoy path that only a scanner would ask forGET /honeypot
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 webrootGET /application.propertieshoneypot
requested a decoy path that only a scanner would ask forGET /database.ymlhoneypot
2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)GET /docker-compose.yamlhoneypot
requested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialshoneypot
2× requested a decoy path that only a scanner would ask for (2 distinct paths)GET /appsettings.Production.jsonhoneypot
requested a config.json file, hoping it exposes API keys or internal settingsGET /config.jsonhoneypot
requested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswdhoneypot
fuzzed a short, random filename looking for a forgotten script that respondsGET /config.phphoneypot
2× requested wp-config.php or a backup copy of it, hoping to read the database password in clear text (2 distinct paths)GET /wp-config.php.bakhoneypot
3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.localhoneypot
requested a .env file, hoping to find API keys or database credentialsGET /.envhoneypot
requested a decoy path that only a scanner would ask forGET /honeypot
16× requested a decoy path that only a scanner would ask for (16 distinct paths)GET /database.ymlhoneypot

Network

ASN
AS201814 MEVSPACE sp. z o.o.
Network type
home broadband
Reverse DNS
none
Country
Bulgaria BG
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.