> For the complete documentation index, see [llms.txt](https://docs.lazarusbounty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazarusbounty.com/lazarusbounty-program.md). # LazarusBounty Program Combating Cybercrime with Transparency Bybit is taking a firm stand against cybercriminals, including the notorious Lazarus Group, with the launch of the **LazarusBounty Program** ([LazarusBounty.com](https://www.lazarusbounty.com/en)). This initiative is dedicated to bringing full transparency to the industry and strengthening security across the crypto ecosystem. As part of this effort, we've developed HackScan, a powerful tool designed to track, expose, and disrupt illicit fund flows, ensuring that bad actors have nowhere to hide. ### **Key Features of the LazarusBounty Program** * **Track Hacker Fund Flows** – Access real-time, publicly available data on hacker addresses and fund movements. * **Monitor Entity Actions** – Gain insights into how industry players respond to illicit activities and foster institutional collaboration. * **Become a Bounty Hunter** – Submit leads on illicit funds and claim bounties upon successful asset recovery. Built on the principle that transparency is the strongest defense, this program ensures every transaction, response, and inaction is recorded—holding all parties accountable. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lazarusbounty.com/lazarusbounty-program.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 `build a script that syncs our docs to a CMS` 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.