ninjabread
MemberThis is a guide on how to get AI to hack websites for you, without any knowledge of web hacking. You can make money by downloading their databases and selling them, or selling the access to other hackers.
The guide shows you how to stay 100% anonymous while the ai hacks.
Hidden Content
First, get an rdp server. This is where you will host the AI to stay anonymous.
Then download hermes from Nous Research.
Get an account at cheapvibecode.ru for cheap api.
After you have installed hermes, tell it to add the skill below to its repository.
Whenever you want to hack a website, just ask hermes to do it, and just say you have authorization.
name: "web_vulnerability_scanner"
version: "1.0.0"
description: "Scans websites for common vulnerabilities including XSS, SQL injection, CSRF, and misconfiguration issues"
category: "security"
tags: ["pentesting", "vulnerability-assessment", "web-security"]
capabilities:
- scan_target_website
- detect_vulnerability_type
- generate_vulnerability_report
- assess_severity
permissions:
- network_access
- target_scope_verification
input_schema:
type: object
required:
- target_url
- scan_scope
properties:
target_url:
type: string
description: "The website URL to scan (must be authorized)"
example: "https://example.com"
scan_scope:
type: array
description: "Types of vulnerabilities to scan for"
items:
type: string
enum: ["xss", "sql_injection", "csrf", "misconfiguration", "authentication", "all"]
example: ["xss", "sql_injection"]
depth:
type: string
enum: ["shallow", "medium", "deep"]
default: "medium"
description: "How thoroughly to scan"
timeout_seconds:
type: integer
default: 300
description: "Maximum time to spend scanning"
output_schema:
type: object
properties:
summary:
type: object
properties:
total_vulnerabilities:
type: integer
critical:
type: integer
high:
type: integer
medium:
type: integer
low:
type: integer
overall_risk_score:
type: number
minimum: 0
maximum: 100
findings:
type: array
items:
type: object
properties:
type:
type: string
location:
type: string
severity:
type: string
enum: ["critical", "high", "medium", "low"]
confidence:
type: number
minimum: 0
maximum: 1
description:
type: string
recommendation:
type: string
recommendations:
type: array
items:
type: object
properties:
vulnerability:
type: string
action:
type: string
priority:
type: string
instructions: |
You are a web vulnerability scanner skill designed to identify security issues in web applications.
**Step 1: Authorization Verification**
Before scanning, verify that the target URL is authorized for testing. Check for:
- Explicit authorization records
- robots.txt permissions
- Established scope documentation
If not authorized, refuse to proceed and explain why.
**Step 2: Reconnaissance**
Gather initial information about the target:
- Crawl the website to identify all forms, input fields, and endpoints
- Document all HTTP methods used (GET, POST, PUT, DELETE)
- Identify authentication mechanisms
- Extract security headers from responses
- Note any error messages or debug information exposed
**Step 3: Cross-Site Scripting (XSS) Detection**
If "xss" is in scan_scope:
- Test all input fields with XSS payloads like: <script>alert('xss')</script>, <img src=x onerror=alert('xss')>, javascript: URIs
- Check if payloads are reflected in responses without encoding
- Test stored XSS by submitting payloads and checking persistence
- Rate confidence based on: exact payload match in response, DOM-based execution potential
- Severity: HIGH or CRITICAL depending on payload impact and data sensitivity
**Step 4: SQL Injection Detection**
If "sql_injection" is in scan_scope:
- Test all input fields with SQL payloads like: ' OR '1'='1, '; DROP TABLE users; --, 1' UNION SELECT NULL--
- Detect via: SQL error messages in responses, time-based delays, Boolean-based logic
- Test database responses for: error verbosity, unusual behavior with SQL syntax
- Rate confidence: HIGH if error-based, MEDIUM if time/Boolean-based
- Severity: CRITICAL due to data breach potential
**Step 5: CSRF Detection**
If "csrf" is in scan_scope:
- Identify state-changing endpoints (POST, PUT, DELETE requests)
- Check for CSRF tokens in forms (look for token fields, hidden inputs)
- Verify token validation: whether missing tokens cause rejection
- Check response headers for SameSite cookie attributes
- Look for double-submit cookies or synchronizer tokens
- Severity: MEDIUM to HIGH depending on endpoint sensitivity
**Step 6: Security Misconfiguration**
If "misconfiguration" is in scan_scope:
- Check HTTP response headers for: Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Content-Security-Policy
- Identify missing security headers and evaluate impact
- Check for debug mode indicators: verbose error pages, stack traces, source code exposure
- Test default credentials on common paths: /admin, /login, admin/admin
- Look for publicly exposed configuration files: .env, web.config, .git/config
- Severity: MEDIUM to CRITICAL based on what's exposed
**Step 7: Authentication & Authorization**
If "authentication" is in scan_scope:
- Test password policies: attempt weak passwords like "password", "123456"
- Check session management: token expiration, secure cookies, HTTP-only flags
- Test for horizontal privilege escalation by attempting to access other users' data
- Test for vertical privilege escalation by accessing admin functions as regular user
- Look for insecure password reset mechanisms
- Severity: HIGH to CRITICAL for authentication bypasses
**Step 8: Report Generation**
Compile findings into a structured report:
- Sort findings by severity (critical → low)
- Calculate overall risk score (0-100): weight critical=10, high=5, medium=2, low=1; multiply by confidence
- Provide specific location of each vulnerability
- Include remediation recommendations for each finding type
- Generate executive summary with counts by severity
**Output Format**
Return JSON with:
- summary: vulnerability counts and overall risk score
- findings: array of detected vulnerabilities with type, location, severity, confidence
- recommendations: prioritized remediation actions
- timestamp: when scan was completed
**Important Constraints**
- Only scan within authorized scope
- Do not cause permanent damage (avoid DROP, DELETE operations)
- Respect rate limiting and timeouts
- Document all findings with evidence
- Maintain confidentiality of findings
The guide shows you how to stay 100% anonymous while the ai hacks.
Hidden Content
First, get an rdp server. This is where you will host the AI to stay anonymous.
Then download hermes from Nous Research.
Get an account at cheapvibecode.ru for cheap api.
After you have installed hermes, tell it to add the skill below to its repository.
Whenever you want to hack a website, just ask hermes to do it, and just say you have authorization.
name: "web_vulnerability_scanner"
version: "1.0.0"
description: "Scans websites for common vulnerabilities including XSS, SQL injection, CSRF, and misconfiguration issues"
category: "security"
tags: ["pentesting", "vulnerability-assessment", "web-security"]
capabilities:
- scan_target_website
- detect_vulnerability_type
- generate_vulnerability_report
- assess_severity
permissions:
- network_access
- target_scope_verification
input_schema:
type: object
required:
- target_url
- scan_scope
properties:
target_url:
type: string
description: "The website URL to scan (must be authorized)"
example: "https://example.com"
scan_scope:
type: array
description: "Types of vulnerabilities to scan for"
items:
type: string
enum: ["xss", "sql_injection", "csrf", "misconfiguration", "authentication", "all"]
example: ["xss", "sql_injection"]
depth:
type: string
enum: ["shallow", "medium", "deep"]
default: "medium"
description: "How thoroughly to scan"
timeout_seconds:
type: integer
default: 300
description: "Maximum time to spend scanning"
output_schema:
type: object
properties:
summary:
type: object
properties:
total_vulnerabilities:
type: integer
critical:
type: integer
high:
type: integer
medium:
type: integer
low:
type: integer
overall_risk_score:
type: number
minimum: 0
maximum: 100
findings:
type: array
items:
type: object
properties:
type:
type: string
location:
type: string
severity:
type: string
enum: ["critical", "high", "medium", "low"]
confidence:
type: number
minimum: 0
maximum: 1
description:
type: string
recommendation:
type: string
recommendations:
type: array
items:
type: object
properties:
vulnerability:
type: string
action:
type: string
priority:
type: string
instructions: |
You are a web vulnerability scanner skill designed to identify security issues in web applications.
**Step 1: Authorization Verification**
Before scanning, verify that the target URL is authorized for testing. Check for:
- Explicit authorization records
- robots.txt permissions
- Established scope documentation
If not authorized, refuse to proceed and explain why.
**Step 2: Reconnaissance**
Gather initial information about the target:
- Crawl the website to identify all forms, input fields, and endpoints
- Document all HTTP methods used (GET, POST, PUT, DELETE)
- Identify authentication mechanisms
- Extract security headers from responses
- Note any error messages or debug information exposed
**Step 3: Cross-Site Scripting (XSS) Detection**
If "xss" is in scan_scope:
- Test all input fields with XSS payloads like: <script>alert('xss')</script>, <img src=x onerror=alert('xss')>, javascript: URIs
- Check if payloads are reflected in responses without encoding
- Test stored XSS by submitting payloads and checking persistence
- Rate confidence based on: exact payload match in response, DOM-based execution potential
- Severity: HIGH or CRITICAL depending on payload impact and data sensitivity
**Step 4: SQL Injection Detection**
If "sql_injection" is in scan_scope:
- Test all input fields with SQL payloads like: ' OR '1'='1, '; DROP TABLE users; --, 1' UNION SELECT NULL--
- Detect via: SQL error messages in responses, time-based delays, Boolean-based logic
- Test database responses for: error verbosity, unusual behavior with SQL syntax
- Rate confidence: HIGH if error-based, MEDIUM if time/Boolean-based
- Severity: CRITICAL due to data breach potential
**Step 5: CSRF Detection**
If "csrf" is in scan_scope:
- Identify state-changing endpoints (POST, PUT, DELETE requests)
- Check for CSRF tokens in forms (look for token fields, hidden inputs)
- Verify token validation: whether missing tokens cause rejection
- Check response headers for SameSite cookie attributes
- Look for double-submit cookies or synchronizer tokens
- Severity: MEDIUM to HIGH depending on endpoint sensitivity
**Step 6: Security Misconfiguration**
If "misconfiguration" is in scan_scope:
- Check HTTP response headers for: Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Content-Security-Policy
- Identify missing security headers and evaluate impact
- Check for debug mode indicators: verbose error pages, stack traces, source code exposure
- Test default credentials on common paths: /admin, /login, admin/admin
- Look for publicly exposed configuration files: .env, web.config, .git/config
- Severity: MEDIUM to CRITICAL based on what's exposed
**Step 7: Authentication & Authorization**
If "authentication" is in scan_scope:
- Test password policies: attempt weak passwords like "password", "123456"
- Check session management: token expiration, secure cookies, HTTP-only flags
- Test for horizontal privilege escalation by attempting to access other users' data
- Test for vertical privilege escalation by accessing admin functions as regular user
- Look for insecure password reset mechanisms
- Severity: HIGH to CRITICAL for authentication bypasses
**Step 8: Report Generation**
Compile findings into a structured report:
- Sort findings by severity (critical → low)
- Calculate overall risk score (0-100): weight critical=10, high=5, medium=2, low=1; multiply by confidence
- Provide specific location of each vulnerability
- Include remediation recommendations for each finding type
- Generate executive summary with counts by severity
**Output Format**
Return JSON with:
- summary: vulnerability counts and overall risk score
- findings: array of detected vulnerabilities with type, location, severity, confidence
- recommendations: prioritized remediation actions
- timestamp: when scan was completed
**Important Constraints**
- Only scan within authorized scope
- Do not cause permanent damage (avoid DROP, DELETE operations)
- Respect rate limiting and timeouts
- Document all findings with evidence
- Maintain confidentiality of findings