drugbank-database
Warn
Audited by Gen Agent Trust Hub on Nov 6, 2026
Risk Level: MEDIUMDYNAMIC_EXECUTIONINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
- [DYNAMIC_EXECUTION]: The skill's data caching strategy in
references/data-access.mdutilizes thepicklemodule. Deserializing data usingpickle.load()is inherently unsafe because it allows for arbitrary code execution if an attacker replaces the local cache file with a malicious payload.- [INDIRECT_PROMPT_INJECTION]: The skill ingests external pharmaceutical data (XML format) from the DrugBank database as seen inreferences/drug-queries.md. It lacks explicit boundary markers or sanitization logic to prevent instructions potentially embedded in that data from overriding agent behavior during interpolation into prompts.- [COMMAND_EXECUTION]: The installation instructions inSKILL.mdandreferences/data-access.mdrequire the user to install multiple external Python packages, includingdrugbank-downloaderandbioversions. While these are standard tools in the bioinformatics domain, they expand the agent's software supply chain risk.- [EXTERNAL_DOWNLOADS]: The skill is designed to download large datasets fromgo.drugbank.com. Although this is a well-known service for medical data, the process involves fetching and processing remote files at runtime which requires network and filesystem access.- [DATA_EXPOSURE]: The documentation inreferences/data-access.mdprovides guidance on managing DrugBank credentials via environment variables and configuration files (~/.config/drugbank.ini). This is noted as a safe practice for secret management compared to hardcoding.
Audit Metadata