45.138.12.49

Blocked Persistent Regular Toolkit

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
Persistent
Attack-shaped requests
234all time
Active days
2UTC days
First seen
Last seen
Servers hit
1
Targets
0sites
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 234 attack-shaped requests across 2 separate days.

Its traffic requested a decoy path that only a scanner would ask for (189 requests); it also requested a .env file, hoping to find API keys or database credentials (24); 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 (17).

Seen by our honeypot sensor.

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

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

Routed via AS218785 (Tc Datacenter Limited), a hosting network.

Surfaces: honeypot. Attack types: leaked-password reuse, scanning, hunting for secrets. Seen by: honeypot.

Activity, last 90 days

Active on 2 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
132
102
  • At least 60 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 232, POST 2.
  • The servers we watch answered: 404 190, 429 44 (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 /var/run/secrets/kubernetes%252eio/serviceaccount/tokenhoneypot
-4× requested a decoy path that only a scanner would ask for (4 distinct paths)GET /%00var/%00run/%00secrets/%00kubernetes.io/%00serviceaccount/%00tokenhoneypot
submitted credentials to a decoy login form designed to capture, never validate, themPOST /honeypot
requested a decoy path that only a scanner would ask forGET /srv/app/secrets%2ejson?honeypot
submitted credentials to a decoy login form designed to capture, never validate, themPOST /honeypot
5× requested a decoy path that only a scanner would ask for (5 distinct paths)GET /app/config%252eyamlhoneypot
requested a .env file, hoping to find API keys or database credentialsGET /%00.envhoneypot
8× requested a decoy path that only a scanner would ask for (8 distinct paths)GET /workspace/settings%252epyhoneypot
requested a .env file, hoping to find API keys or database credentialsGET /srv/app/.env?honeypot
19× requested a decoy path that only a scanner would ask for (19 distinct paths)GET /srv/app/secrets.jsonhoneypot
requested a decoy path that only a scanner would ask forGET /srv/app/application.yamlhoneypot
requested a .env file, hoping to find API keys or database credentialsGET /opt/app/.env.developmenthoneypot
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 /%00opt/%00tomcat/%00webapps/%00ROOT/%00settings.pyhoneypot
5× requested a decoy path that only a scanner would ask for (5 distinct paths)GET /%00usr/%00src/%00app/%00local.settings.jsonhoneypot

Network

ASN
AS218785 Tc Datacenter Limited
Network type
hosting
Reverse DNS
none
Country
Lithuania LT
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.