91.92.242.37

Blocked Brute

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

Record

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

First seen on UTC, most recently active on UTC.

Recorded 126 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (126 requests).

Seen by our honeypot sensor.

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

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

Routed via AS202412 (Omegatech LTD), a hosting network.

Surfaces: honeypot. Attack types: hunting for secrets. Seen by: honeypot.

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
126
  • At least 126 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 126.
  • The servers we watch answered: 429 66, 404 59, 200 1 (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
50× requested a .env file, hoping to find API keys or database credentials (50 distinct paths)GET /www/.env.swphoneypot

Network

ASN
AS202412 Omegatech LTD
Network type
hosting
Reverse DNS
none
Country
The Netherlands NL
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.