34.89.147.128

Blocked Persistent Night Owl Toolkit

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

Record

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

First seen on UTC, most recently active on UTC.

Recorded 261 attack-shaped requests across 1 separate day.

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

Seen by our edge and web sensors, against 2 of the sites we watch: 4emx.com and schetio.com.

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

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

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

Surfaces: honeypot, web-app. Attack types: fake crawlers, known exploits, injection, scanning, hunting for secrets. 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
261
  • At least 254 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 342, POST 32, DELETE 1.
  • The servers we watch answered: 404 252, 403 7, 200 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
schetio.com3× made a request that matched no known pattern (2 distinct paths)POST /webhook-test/declared botedge
schetio.com2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)POST /cgi-bin/phpdeclared botedge
schetio.commade a request that matched no known patternPOST /api/v1/node-load-method/customMCPdeclared botedge
schetio.comtried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute codePOST /cgi-bin/php-cgi.exedeclared botedge
schetio.com2× tried to abuse a local or remote file inclusion parameter such as allow_url_include (2 distinct paths)POST /index.phpdeclared botedge
schetio.com5× made a request that matched no known pattern (5 distinct paths)POST /api/templates/previewdeclared botedge
schetio.commade a request that matched no known patternDELETE /api/inngestdeclared botedge
schetio.com2× made a request that matched no known pattern (2 distinct paths)POST /dashboarddeclared botedge
schetio.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/..%252f..%252f..%252f..%252f..%252froot/.envdeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.localdeclared botedge
schetio.commade a request that matched no known patternGET /.bashrcdeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.envdeclared botedge
schetio.commade a request that matched no known patternGET /.vault-tokendeclared botedge
schetio.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /@fs/.envdeclared botedge
schetio.com2× made a request that matched no known pattern (2 distinct paths)GET /.zshrcdeclared botedge
schetio.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURLdeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /@fs/.envdeclared botedge
schetio.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/../.envdeclared botedge
schetio.com3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.developmentdeclared botedge
schetio.com2× made a request that matched no known pattern (2 distinct paths)GET /.github/workflows/deploy.ymldeclared botedge
schetio.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /frontend/.envdeclared botedge
schetio.commade a request that matched no known patternGET /service-account.jsondeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /.envdeclared botedge
schetio.comclaimed to be Bingbot while requesting an admin or credentials path the real crawler never touchesGET /.env.production.localdeclared botedge
schetio.comprobed for an exposed .git directory to download the site's source history and configGET /.git/HEADdeclared botedge
schetio.commade a request that matched no known patternGET /.npmrcdeclared botedge
schetio.comrequested a .env file, hoping to find API keys or database credentialsGET /public/.envdeclared botedge
schetio.com2× made a request that matched no known pattern (2 distinct paths)GET /.aws/configdeclared botedge
schetio.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswddeclared botedge
schetio.com4× made a request that matched no known pattern (4 distinct paths)GET /firebase-service-account.jsondeclared botedge

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
128.147.89.34.bc.googleusercontent.com
Country
Germany DE
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.