Score-based assessment (critical risk, 100/100). An AI review is available in the AI review tab.
Analysis record
- Analysed
- 2 months ago 26 August 2026
- Version
- v2.1.0
- Artifact
- SHA256 b9824900…7b318b
- Detail
- Full list
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
YARA Rule Matches
8 rules| Severity | Rule | Hits | Files | Metadata |
|---|---|---|---|---|
| LOW | postinstall file download | 18 | dist/types/bo-package-data.d.tsdist/types/bo-configuration.d.tsdist/types/dto-component.d.ts +15 more | - |
| LOW | postinstall environment access | 14 | dist/types/dto-integration.d.tsdist/types/dto-component.d.tsdist/types/vo-template.d.ts +11 more | - |
| LOW | postinstall network communication | 18 | dist/api/package/configuration-instance.d.tsdist/types/dto-component.d.tsdist/types/bo-zapier.d.ts +15 more | - |
| LOW | postinstall file manipulation | 19 | dist/types/dto-package.d.tsdist/types/bo-configuration.d.tsdist/types/bo-package-data.d.ts +16 more | - |
| LOW | postinstall crypto operations | 1 | dist/react/index.esm.js | - |
| LOW | postinstall registry modification | 2 | README.mddist/types/index.esm.js | - |
| LOW | postinstall obfuscation | 2 | dist/react/index.esm.jsdist/types/index.esm.js | - |
| LOW | postinstall system command | 5 | dist/api/package/package.d.tsREADME.mddist/api/index.esm.js +2 more | - |
Finding Categories
YARA Rules Matched
8 rules(79 hits)MCP Server Analysis
MCP servers expose tools and resources to AI assistants. Unlike browser extensions, they run as standalone processes with direct system access. Tool definitions are analyzed for prompt injection, data exfiltration, and tool poisoning patterns.
AI Security Report
AI Security Review
Summary
ToolSDK.ai MCP server scores CRITICAL with tool-poisoning detected, 79 malware signatures, and 217 IoC matches. The credential-access findings are spread across type definition files (.d.ts) which is likely pattern-matching on field names like credentials in an integration SDK — expected for a platform offering 100+ third-party integrations. The 2 tool-poisoning findings warrant direct inspection. Malware signatures and IoC volume need source review before escalating.
Key Reasons
- Tool-poisoning detected (2 findings) — direct risk for AI agent manipulation; requires manual inspection of the specific tool descriptions
- 79 malware signatures fired — high volume but no confirmed malware_detected flag; likely broad YARA rules hitting minified SDK bundle
- 217 IoC matches on an integration SDK are plausible (100+ external service endpoints) but need filtering for genuinely malicious indicators
- Credential-access findings are all in .d.ts type definitions referencing a
credentialsfield — almost certainly a false positive from keyword matching on a legitimate auth abstraction
Reviewed 2026-03-13 · version 2.1.0; recommended action: manual reanalysis; model confidence 72%.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace