> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/whats-new/previous-releases/1.15-to-1.43/version-1.36.md).
# Version 1.36
This release was a little lighter than usual…because we spent half of it doing something pretty cool: Hack Week. Check out our recap blog: [Hack Week 2025](https://material.security/resources/hack-week-2025-recap).
## :tada: New
### Account Login Detections
We added some new detections to spot sketchy account activity before it becomes a headache (or a headline):
* **Logins from networks hammering away with brute force attacks**
* `Google account accessed from a network with observed brute force login attempts`
* `Microsoft account accessed from a network with observed brute force login attempts`
* **Logins coming from scraping infrastructure**
* `Google account accessed from a network with observed automated web scraping`
* `Microsoft account accessed from a network with observed automated web scraping`
* **Logins via the** [**TOR**](#user-content-fn-1)[^1] **network**
* `Google account accessed through Tor`
* `Microsoft account accessed through Tor`
### IP Address Evidence Cards
Logs that mention suspicious IPs no longer leave you guessing. Now, issues that involve IP evidence display rich network info, including risk indicators.
***
## 🛠Enhancements
* Some small bug fixes and UI touch-ups (pixels matter, too)
* Heuristic phishing rules tuned up for sharper, faster performance
[^1]: Tor is an anonymous overlay network that obscures the source and destination of internet traffic. Its usage for commercial work is suspect as its primary use is to evade digital surveillance techniques. Some internal teams may require the use of Tor for sensitive communications.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.material.security/whats-new/previous-releases/1.15-to-1.43/version-1.36.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
