@securevector/n8n-nodes-securevector
v0.1.4
Published
SecureVector AI security scanning for n8n workflows - detect prompt injection, jailbreak_attempts, malicious content and more.. See LICENSE.
Maintainers
Readme
n8n-nodes-securevector
AI prompt security scanning for n8n workflows. Detect prompt injection, jailbreak attempts, and 17+ threat categories in real-time.
⚠️ LEGAL DISCLAIMER: This software is provided "AS-IS" without warranties. SecureVector makes NO guarantees about security effectiveness. Users assume ALL risk and liability. See License for full terms.
Quick Start
Installation
Via n8n Community Nodes (Recommended):
- Go to Settings → Community Nodes → Install
- Enter:
@securevector/n8n-nodes-securevector - Restart n8n
Via npm:
cd ~/.n8n && npm install @securevector/n8n-nodes-securevectorSetup
- Get API key:
- Direct link: https://app.securevector.io/dashboard?section=access
- Or navigate: SecureVector App → Access Management → Create API Key
- Add SecureVector node to workflow
- Configure credentials (API key format:
sv_xxxxx)
Operation Modes
| Mode | Use Case | Behavior | Configuration | Diagram |
|------|----------|----------|---------------|---------|
| Non-Blocking | Analysis & logging | Returns scan results, workflow continues regardless of threat | Block on Threat: OFF | Trigger → SecureVector → Next Node |
| Blocking | Security gate | Stops workflow if threat detected | Block on Threat: ONThreshold: 0-100Risk Levels: Select | Trigger → SecureVector → [STOP if threat] → Next Node |
| Parallel | Real-time monitoring | Scan + LLM run simultaneously | Block on Threat: OFFSplit workflow | Trigger ──┬→ SecureVector └→ LLM → Merge |
Mode Details
🔓 Non-Blocking (Default)
User Input → SecureVector Scan → IF Node (score > 50?)
├─ TRUE → Alert Team
└─ FALSE → Send to LLMUse for: Logging, metrics, conditional routing
🔒 Blocking (Security Gate)
User Input → SecureVector Scan → LLM Processing
[THROWS ERROR IF THREAT DETECTED - WORKFLOW STOPS]Use for: Preventing malicious prompts from reaching LLM
⚡ Parallel (Async Analysis)
User Input ──┬→ SecureVector Scan ──┐
└→ LLM Processing ──────→ Merge → ResultsUse for: Performance-critical workflows
Parameters
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| prompt | string | - | Text to scan (max 10,000 chars, truncated if longer) |
| timeout | number | 30 | Scan timeout in seconds (1-300) |
| includeMetadata | boolean | false | Include workflow ID in request |
| blockOnThreat | boolean | false | Stop workflow on threat detection |
| threatThreshold | number | 50 | Score threshold for blocking (0-100) |
| blockOnRiskLevels | array | ['critical', 'high'] | Risk levels that trigger blocking |
Output Format
{
"scanId": "550e8400-e29b-41d4-a716-446655440000",
"score": 85,
"riskLevel": "high",
"threats": [
{
"category": "prompt_injection",
"severity": "high",
"title": "Potential prompt injection detected",
"description": "...",
"confidence": 0.92
}
],
"timestamp": "2025-12-27T10:30:00.000Z",
"metadata": {
"processingTimeMs": 150,
"version": "1.0.0"
}
}Scoring: 0 = safe, 100 = maximum threat
Risk Levels: safe, low, medium, high, critical
17 Threat Categories: prompt_injection, adversarial_attack, model_extraction, data_poisoning, privacy_leak, bias_exploitation, model_inversion, membership_inference, backdoor_attack, evasion_attack, jailbreak_attempt, sensitive_data_exposure, inappropriate_content, malicious_code_generation, social_engineering, misinformation_generation, privilege_escalation
Data Privacy
What data is sent to SecureVector API?
This node sends ONLY the following data to the SecureVector API for analysis:
- Input data - Any content you provide in the
promptparameter (text, prompts, data, or any other input you want analyzed) - Metadata (optional) - Only if
includeMetadatais enabled:- Workflow ID
- Execution ID
- Source identifier (
n8n-workflow)
Why is this data sent and stored?
- Analysis: Your input is analyzed for security threats and returned with a threat score
- Your auditing: All data you send is persisted for your own logging and auditing purposes - this allows you to review scan history, track which workflows triggered scans, and maintain audit trails
What is NOT sent?
- API keys or credentials
- Other node data or variables not explicitly provided
- Workflow configuration or logic
- Any data from other nodes in your workflow
Important: Anything you send for analysis will be stored by SecureVector for your auditing and logging purposes. Only send data you consent to being analyzed and stored.
Data retention: See SecureVector Privacy Policy for details on how scan data is stored and retained.
Examples
See examples/ for importable n8n workflow JSON files:
non-blocking-analysis.json- Conditional routing patternblocking-mode.json- Security gate patternparallel-analysis.json- Async scanning pattern
Troubleshooting
| Issue | Solution |
|-------|----------|
| "Invalid API key" | Verify key format: sv_xxxxx at app.securevector.io |
| "Timeout" | Increase timeout parameter or check network |
| "Rate limit exceeded" | Wait 60s or upgrade plan |
| Node not appearing | Restart n8n after installation |
Support
- Documentation: docs.securevector.io
- Issues: GitHub Issues
- Security: Report to [email protected] (see SECURITY.md)
Development
git clone https://github.com/Secure-Vector/n8n-nodes-securevector.git
cd n8n-nodes-securevector
npm install
npm test # Run tests
npm run build # Build dist/
npm link # Link to local n8nSee CONTRIBUTING.md for guidelines.
License
Licensed under MIT License.
DISCLAIMER
THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
SecureVector makes NO representations or warranties about:
- The accuracy, reliability, or completeness of security scans
- The detection or prevention of security threats
- The suitability for any particular purpose
Users assume ALL risk and liability for:
- Use of this software in production environments
- Any security breaches, data loss, or damages
- Compliance with applicable laws and regulations
This node is a TOOL ONLY. It does not guarantee security. Users are solely responsible for implementing comprehensive security measures.
By using this software, you acknowledge that SecureVector shall not be liable for any claims, damages, or losses arising from its use.
Copyright © 2025 SecureVector. All rights reserved.
Security Notes
Development Dependencies
npm audit may show a critical vulnerability in form-data (via n8n-workflow). This does not affect the published package because:
n8n-workflowis a peer dependency (provided by n8n runtime, not bundled)- Our package only bundles
zod(no vulnerabilities) - Our code uses JSON requests, not multipart/form-data
- The vulnerability would need to be fixed in n8n core, not this package
For the latest security updates, keep your n8n installation up to date.
Reporting Security Issues
Report security issues to: [email protected]
