35.201.181.14

Blocked Persistent Toolkit

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

Record

Score
42/100each request counts half as much after 30 days
Worst level
Persistent
Attack-shaped requests
264all 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 264 attack-shaped requests across 1 separate day.

Its traffic requested a .env file, hoping to find API keys or database credentials (139 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 techauthors.eu.

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

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

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

Surfaces: 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
264
  • At least 144 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 251, POST 16.
  • The servers we watch answered: 404 246, 403 24 (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
techauthors.euclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /webhook-test/declared botweb
techauthors.eu2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)POST /cgi-bin/php?declared botweb
techauthors.eufuzzed a short, random filename looking for a forgotten script that respondsPOST /index.php?declared botweb
techauthors.eu2× tried to abuse a PHP-CGI argument-injection flaw (allow_url_include/auto_prepend_file) to execute code (2 distinct paths)POST /cgi-bin/php?declared botweb
techauthors.eutried to abuse a local or remote file inclusion parameter such as allow_url_includePOST /php-cgi/php-cgi.exe?declared botweb
techauthors.eufuzzed a short, random filename looking for a forgotten script that respondsPOST /index.php?declared botweb
techauthors.eu2× swept a generic login/signup/account/dashboard route this site does not expose, consistent with an automated app-framework scanner/apinoneweb
techauthors.euclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /api/functionRouterdeclared botweb
techauthors.eurequested 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 /firebase-config.jsdeclared botweb
techauthors.eurequested a .env file, hoping to find API keys or database credentialsGET /application/.env.sampledeclared botweb
techauthors.eu3× made a request that matched no known pattern (3 distinct paths)GET /config/environment.jsondeclared botweb
techauthors.eutriggered Cloudflare's managed rule for a Next.js server-action request-smuggling/RCE attemptPOST /api/authdeclared botedge
techauthors.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.dev.ymldeclared botweb
techauthors.eurequested 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 /.docker/secrets.jsondeclared botweb
techauthors.eu4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /application/.envdeclared botweb
techauthors.eumade a request that matched no known patternGET /.gitconfigdeclared botweb
techauthors.eu4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /config/.env.localdeclared botweb
techauthors.eumade a request that matched no known patternGET /samconfig.tomldeclared botweb
techauthors.eu3× requested a .env file, hoping to find API keys or database credentials (3 distinct paths)GET /.env.dockerdeclared botweb
techauthors.eurequested 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 /firebaseConfig.jsdeclared botweb
techauthors.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.production.ymldeclared botweb
techauthors.eurequested a .env file, hoping to find API keys or database credentialsGET /.env.sesdeclared botweb
techauthors.eurequested docker-compose.yml, which often contains embedded passwords and connection stringsGET /docker-compose.staging.ymldeclared botweb
techauthors.eumade a request that matched no known patternGET /terraform.tfstate.backupdeclared botweb
techauthors.eu6× requested a .env file, hoping to find API keys or database credentials (6 distinct paths)GET /.env.maildeclared botweb
techauthors.eu2× requested docker-compose.yml, which often contains embedded passwords and connection strings (2 distinct paths)GET /docker-compose.override.ymldeclared botweb
techauthors.eu4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /.env.stagedeclared botweb
techauthors.euprobed for an exposed .svn directory to read the site's version-control metadata/.svnnoneweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
14.181.201.35.bc.googleusercontent.com
Country
Taiwan TW
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.