Based on the RiskyPlugins AI security review of the observed evidence.
No individual score drivers were recorded for this analysis.
Analysis record
- Analysed
- 8 months ago 9 March 2026
- Version
- v26.2.1
- Artifact
- SHA256 e960a13d…dba885
- Detail
- Full list
No findings
The analyzer reported nothing for this version.
No findings
The analyzer reported nothing for this version.
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality strong.
Security Analysis: @borgius/n8n-nodes-planka
Tool-Poisoning Assessment
No tool-poisoning findings detected. The evidence bundle shows "tool-poisoning":0 in the threat_indicators. This is the defining MCP threat category, and its complete absence is a strong indicator of benign behavior. There are no findings with titles suggesting hidden AI directives, invisible Unicode characters, or XML-style instruction tags in tool metadata.
Credential and Network Access
No credential or network findings. The findings_summary shows:
"secret":0- no credential access findings"network":0- no HTTP/fetch/socket calls to external domains"ioc":399- all medium-severity SHA256 hash findings
The 399 IoC findings are exclusively SHA256 hashes (e.g., XIOC-SHA256-0ce71e5ee7c489209494c14028e351ccb1ffe455187d98a889f8e07ae2458ef7, XIOC-SHA256-db3ea1212b188ff23aa4f32b63e459c9b55d34b44b57bcbdf401f291352483f0). These are file content hashes, not network destinations. Without accompanying network findings showing calls to suspicious domains, SHA256 hash IoCs are meaningless noise.
The absence of credential-access findings targeting sensitive paths (.ssh/, .aws/credentials, .kube/config) and the absence of network findings means there is no exfiltration architecture present.
Code-Smell Findings
15 low-severity code-smell findings are present but these are explicitly documented noise sources. The guidelines state: "YARA code-smell rules fire on almost any non-trivial JavaScript" and "should NEVER drive a verdict." These findings match basic Node.js patterns (fetch, exec, fs, crypto, process.env) that every legitimate n8n node requires.
Strongest Counterargument
The counterargument is the high finding count (414 total) and 0 user count, which could indicate an unvetted package. However, the finding count is entirely from SHA256 hash IoCs (file content hashes from bundled dependencies) and code-smell rules (documented noise). The 0 user count simply indicates a new or niche package, not malicious intent. Without tool-poisoning, credential access, or network exfiltration findings, the high count is irrelevant.
Conclusion
This n8n community node for Planka integration shows no evidence of malicious behavior. All findings are false positives from bundled dependencies (SHA256 hashes) or documented code-smell noise. The package performs its stated function without hidden AI directives, credential theft, or data exfiltration.
Key Reasons
- Zero tool-poisoning findings (defining MCP threat absent)
- Zero credential/secret findings (no credential access)
- Zero network findings (no exfiltration architecture)
- Zero malware-signature findings
- All 399 IoC findings are benign SHA256 file hashes
False Positive Considerations
- SHA256 hash IoCs from bundled dependencies
- Code-smell YARA rules matching standard Node.js patterns
Reviewed 2026-04-27 · version 26.2.1; recommended action: suppress false positive; model confidence 85%.
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