> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/compliance-and-reporting/reports/malware-monitor-report.md).
# Malware Monitor Report
The [Malware Monitor](https://app.aikido.dev/reports/malware/software-supply-chain-attacks) gives you visibility into malicious packages published in public registries and shows whether they affect your environment.
Aikido continuously compares your dependencies against a live feed of known malicious packages across ecosystems such as npm, PyPI, NuGet, Maven, RubyGems, VS Code extensions, and more.
If a malicious package is detected in your projects, you are alerted immediately. Use [Safe-Chain to block Malware](/code-scanning/aikido-malware-scanning.md) from getting installed on your machines.
## When to use this report
Use the Malware Monitor when you need to:
* Detect malicious open source packages before they cause damage
* Respond to supply chain incidents
* Demonstrate protection against dependency based attacks
* Monitor newly published threats in public registries
* Reassure customers about third party risk
This report focuses specifically on intentional malware, not regular vulnerabilities.
---
# 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://help.aikido.dev/compliance-and-reporting/reports/malware-monitor-report.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.
