> For the complete documentation index, see [llms.txt](https://docs.ironblocks.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ironblocks.com/platform/threat-detection/detectors-library.md).

# Detectors Library

Detectors Library: displays available pre-built detectors. (Initially, you can "Expand" on the preferred detector to review its application in the Documentation).

<figure><img src="/files/W4SdENqWD5oZZGVi7kkN" alt=""><figcaption></figcaption></figure>

Ironblocks' Threat Detection utilizes a wide range of sophisticated detectors, each tailored to identify specific threats or suspicious activities within transactions. Below, you'll find a description of each detector, explaining their behavior and how they contribute to enhancing your security. Understanding the capabilities of these detectors allows you to effectively configure and leverage the system to safeguard your blockchain applications.

## **1. Drastic Balance Change**

Triggered when a set amount of funds dollar value moves in or out of a contract. It works by aggregating well-know token and ETH value against real-time USD value, and comparing that against the configured threshold. The Drastic Balance Change detectors is crucial for identifying anomalies in transaction volumes that could indicate unauthorized withdrawals or other irregular activities.

## **2. Reentrancy**

The Reentrancy detector is activated when an external contract makes a callback to your smart contract. It also supports whitelisting authorized contracts, in case your application needs to allow it. This detector is essential for identifying and preventing reentrancy attacks, a common vulnerability exploited in smart contracts.

## **3. New S**uspicious **Contract**

This detector is activated when your contract interacts with a newly created contract, specifically those created within the last 24 hours. It helps in monitoring and mitigating risks associated with interactions involving newly deployed and potentially malicious contracts.

## **4. Admin Calls**

Activated when a transaction involves one of the pre-configured admin accounts, this detector is crucial for monitoring and preventing unauthorized access and potential private key theft. It ensures that only authorized actions are taken by admin accounts.

## **5. Flashloan**

This detector is triggered when a transaction includes a flashloan - a type of loan in decentralized finance (DeFi) applications which is issued and settled within a single transaction. It's important for monitoring and responding to the unique risks associated with flashloan-based attack vectors - such as price manipulation attacks.

## **6. Mixer**

The Mixer detector is activated when transactions involve wallets that have previously been flagged as malicious or when funds have passed through a mixer, which can obscure the origins of the funds. This detector is vital for tracking and mitigating the risks associated with unsanctioned funds that come from mixers.&#x20;