34.50.109.24

Blocked Persistent 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
Persistent
Attack-shaped requests
131all 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 131 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (28 requests); 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 (26); it also requested wp-config.php or a backup copy of it, hoping to read the database password in clear text (11); 28 requests matched no known pattern.

Seen by our edge and web sensors, against victorantonov.com.

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

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

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

Surfaces: web-app. Attack types: hunting for secrets, unclassified. 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
131
  • At least 71 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 148.
  • The servers we watch answered: 404 65, 403 6 (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
victorantonov.com4× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (4 distinct paths)/.zsh_historynoneweb
victorantonov.commade a request that matched no known patternGET /sftp-config.jsonbrowser claimweb
victorantonov.com3× probed a Spring Boot actuator endpoint, which can leak environment variables and internal config if left open (2 distinct paths)GET /actuator/configpropsbrowser claimweb
victorantonov.com7× requested docker-compose.yml, which often contains embedded passwords and connection strings (4 distinct paths)GET /docker-compose.override.ymlbrowser claimweb
victorantonov.com4× made a request that matched no known pattern (2 distinct paths)GET /kubeconfigbrowser claimweb
victorantonov.com3× requested a private SSH key file by its conventional name (2 distinct paths)GET /id_ed25519browser claimweb
victorantonov.com2× made a request that matched no known patternGET /secrets.yamlbrowser claimweb
victorantonov.com4× 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 (2 distinct paths)GET /secrets.ymlbrowser claimweb
victorantonov.com2× was blocked at the edge without matching any specific attack signatureGET /.envrcbrowser claimedge
victorantonov.comsent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked/.s3cmd.ininoneweb
victorantonov.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswdbrowser claimweb
victorantonov.comsent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked/.netrcnoneweb
victorantonov.com2× was blocked at the edge without matching any specific attack signatureGET /.git-credentialsbrowser claimedge
victorantonov.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswdbrowser claimweb
victorantonov.comsent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked/.kube/confignoneweb
victorantonov.com2× requested a config.json file, hoping it exposes API keys or internal settingsGET /.docker/config.jsonbrowser claimweb
victorantonov.commade a request that matched no known patternGET /.kube/configbrowser claimweb
victorantonov.com2× 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 /.aws/configbrowser claimweb
victorantonov.com2× requested an AWS credentials file left in a web-accessible path by mistakeGET /.aws/credentialsbrowser claimweb
victorantonov.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 /.jest.config.jsbrowser claimweb
victorantonov.com3× sent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked (3 distinct paths)/.eslintrc.jsonnoneweb
victorantonov.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 /webpack.config.jsbrowser claimweb
victorantonov.comsent a request whose combined suspicious-pattern score crossed the web firewall's alert threshold; the request was observed and not blocked/package.jsonnoneweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
24.109.50.34.bc.googleusercontent.com
Country
Indonesia ID
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.