8.229.153.6

Blocked Persistent Regular Night Owl Toolkit

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

Record

Score
50/100each request counts half as much after 30 days
Worst level
Persistent
Attack-shaped requests
291all time
Active days
2UTC days
First seen
Last seen
Servers hit
2
Targets
1site
Times blocked
1by the evidence rules

First seen on UTC, most recently active on UTC.

Recorded 291 attack-shaped requests across 2 separate days.

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

Seen by our edge and web sensors, against zmey.eu.

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

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

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

Surfaces: honeypot, web-app. Attack types: injection, scanning, hunting for secrets, unclassified. Seen by: edge, web.

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
244
47
  • At least 179 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 345, POST 1.
  • The servers we watch answered: 404 247, 403 6, 200 4 (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
zmey.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.production.ymldeclared botedge
zmey.eu2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)GET /Dockerrun.aws.jsondeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /temp/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /private-keydeclared botedge
zmey.eu3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /etc/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /configuration.php.bakdeclared botedge
zmey.eurequested wp-config.php or a backup copy of it, hoping to read the database password in clear textGET /wp-config.php~declared botedge
zmey.eu5× was turned away at the edge because the address is already on our block list; not counted as new evidence (5 distinct paths)GET /.profiledeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /api/.envdeclared botedge
zmey.eu2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)GET /config/local.jsondeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /apps/docs/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /account/_payload.jsondeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /config/env/aws_credentials.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /ssl/localhost.keydeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.wwwdeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /api/w/starter/jobs_u/get_log_file/../../../../proc/self/environdeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /private/.envdeclared botedge
zmey.euprobed for an exposed .svn directory to read the site's version-control metadataGET /.svn/entriesdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.bash_profiledeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env.productiondeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /storage/logs/laravel.logdeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /process.envdeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfiles/xdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /secrets.jsondeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfiles/xdeclared botedge
zmey.eurequested wp-config.php or a backup copy of it, hoping to read the database password in clear textGET /wp-config.php.swpdeclared botedge
zmey.eu3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /site/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /settings/_payload.jsondeclared botedge
zmey.eu2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /dashboard/.envdeclared botedge
zmey.euwas turned away at the edge because the address is already on our block list; not counted as new evidenceGET /.env_secretdeclared botedge
zmey.euused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /userfilesdeclared botedge
zmey.eu2× was turned away at the edge because the address is already on our block list; not counted as new evidence (2 distinct paths)GET /.docker/config.jsondeclared botedge
zmey.eurequested wp-config.php or a backup copy of it, hoping to read the database password in clear textGET /wp-config.php.bakdeclared botedge
zmey.eurequested a .env file, hoping to find API keys or database credentialsGET /.env.proddeclared botedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
6.153.229.8.bc.googleusercontent.com
Country
United States US
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.