# Consistent Unauthorized Access Attempts on Auth0 /authorize Endpoint - Possible Bot Activity

**URL:** <https://community.auth0.com/t/consistent-unauthorized-access-attempts-on-auth0-authorize-endpoint-possible-bot-activity/182088>\
**Category:** Get Help\
**Tags:** bot-detection, attack-protection\
**Created:** [February 13, 2025, 6:00am UTC](https://community.auth0.com/t/consistent-unauthorized-access-attempts-on-auth0-authorize-endpoint-possible-bot-activity/182088 "2025-02-13T06:00:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![brijesh2](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/brijesh2/32/72887_2.png) [@brijesh2](https://community.auth0.com/u/brijesh2)\
**Post date:** [February 13, 2025, 6:00am UTC](https://community.auth0.com/t/consistent-unauthorized-access-attempts-on-auth0-authorize-endpoint-possible-bot-activity/182088/1 "2025-02-13T06:00:43Z")

</div>

We’re seeing **unauthorized requests** consistently targeting our Auth0’s `/authorize` endpoint over the past few days. These requests originate from different IPs and attempt various **unauthorized redirect URLs**. Some requests even use malformed **client IDs** , like `<my_client_id>/robots.txt`. All attempts are failing, but this seems to be **automated bot activity probing for vulnerabilities**.

#### **These are our observations**

- **Unauthorized callback attempts:** (e.g., `https://44.242.57.79/callback`, `https://beta.minerva-development.amazonaws.com/callback`)

- **Multiple source IPs:** (`123.160.223.74`, `101.36.106.89`, etc.)

- **Bots using `Go-http-client 1.1.0` and malformed `client_id/robots.txt` requests.**

- Has anyone else faced **attacks** like this?

- What can we do to **block these attempts**?

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [February 14, 2025, 11:31pm UTC](https://community.auth0.com/t/consistent-unauthorized-access-attempts-on-auth0-authorize-endpoint-possible-bot-activity/182088/3 "2025-02-14T23:31:48Z")

</div>

Hi @brijesh2,

Welcome to the Auth0 Community!

I have just reviewed your tenant logs and noticed the same types of logs you mentioned, specifically with Callback URL mismatch errors.

Usually, when your app calls the login page, the request URL points to the `/authorize` endpoint with all of the correct values for the `domain,` `client_id,` `audience,` `redirect_uri,` etc. Exposing the `/authorize` endpoint is not inherently dangerous since it is intentionally public as part of the OIDC and OAuth 2.0 flow.

However, this could become a threat if an attacker is able to successfully access your login page (`/authorize`) and then perform an attack on your users.

In this case, you should enable the features available in [Attack Protection](https://auth0.com/docs/secure/attack-protection). I see that you already have these features enabled, so your application is protected here.

At this point, Auth0 will continue to log these failed login events and prevent them from accessing your login page.

Let me know if you have any follow-up questions.

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 28, 2025, 11:32pm UTC](https://community.auth0.com/t/consistent-unauthorized-access-attempts-on-auth0-authorize-endpoint-possible-bot-activity/182088/4 "2025-02-28T23:32:25Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
