136.108.186.239

Blocked Brute 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
258all 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 258 attack-shaped requests across 1 separate day.

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

Scored into the "Brute" level now; the highest it has reached is "Persistent". Badge: Toolkit.

Its busiest hour on record began UTC, with 258 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
258
  • At least 160 requests a minute at its peak ( UTC; identical requests in the same second are stored once).
  • Methods: GET 250, POST 15.
  • The servers we watch answered: 404 236, 403 25, 301 2 (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
neutralizatori.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/php?declared botweb
neutralizatori.comtried to abuse a local or remote file inclusion parameter such as allow_url_includePOST /index.php?declared botweb
neutralizatori.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/php?declared botweb
neutralizatori.comtried to abuse a local or remote file inclusion parameter such as allow_url_includePOST /php-cgi/php-cgi.exe?declared botweb
neutralizatori.comtried to abuse a local or remote file inclusion parameter such as allow_url_includePOST /index.php?declared botweb
neutralizatori.comclaimed to be Googlebot while POSTing, something the real crawler never doesPOST /api/fs/execdeclared botweb
neutralizatori.com14× requested a .env file, hoping to find API keys or database credentials (11 distinct paths)GET /@fs/root/.env?declared botweb
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /.env.local?declared botweb
neutralizatori.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 /push_config.jsondeclared botweb
neutralizatori.com2× requested a .env file, hoping to find API keys or database credentials (2 distinct paths)GET /.env?declared botweb
neutralizatori.comrequested .htaccess or .htpasswd, which can leak access rules or password hashesGET /.htpasswddeclared botweb
neutralizatori.comtried to read /proc/self/environ to dump process environment variables, usually via a traversal or inclusion flawGET /@fs/proc/self/environ?declared botweb
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
neutralizatori.com2× requested a .env file, hoping to find API keys or database credentialsGET /@fs/.env?declared botweb
neutralizatori.com2× requested the .git directory itself, hoping it is exposed and browsable/.gitnoneweb
neutralizatori.comrequested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /.env?declared botweb
neutralizatori.com3× requested a Vite/React-Server-Components source map, likely while mapping the app's bundled sourceGET /__vite_rsc_findSourceMapURL?declared botweb
neutralizatori.com3× used Vite dev server's @fs/ path to try to read arbitrary files outside the project root (3 distinct paths)GET /@fs/proc/self/cmdline?declared botweb
neutralizatori.comused a directory-traversal segment (literal or percent-encoded ../) in the request path to try to escape the web rootGET /@fs/../.env?declared botweb
neutralizatori.com4× requested a .env file, hoping to find API keys or database credentials (4 distinct paths)GET /@fs/src/.env?declared botweb
neutralizatori.comrequested an AWS credentials file left in a web-accessible path by mistakeGET /@fs/home/ec2-user/.aws/credentials?declared botweb
neutralizatori.comrequested a .env file, hoping to find API keys or database credentialsGET /@fs/.env?declared botweb
neutralizatori.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 /config/gcp-credentials.jsondeclared botweb

Network

ASN
AS396982 Google LLC
Network type
cloud
Reverse DNS
239.186.108.136.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.