S.01For no-code & automation teams

Security testing, in your workflow

You already orchestrate work in n8n. Darkmoon ships a community node so a pentest becomes just another step: trigger it, collect findings, and route the fix pull requests from its paid Pro remediation tier to whoever should review them.

1
n8n community node on npm
4
Operations: Finding, Retest, Metric, Webhook
4
Schedules: none, daily, weekly, monthly
0
Auto-merges: every fix is a reviewed PR
S.03Your wedge

A node, not a project

Automation teams should not have to write a client to run a pentest.

One n8n node

n8n-nodes-darkmoon triggers a Darkmoon pentest, retrieves its findings, and surfaces the fix pull requests its paid Pro remediation tier prepares, inside your existing flows.

Learn more

S.04What you get
What the node lets you build

01
$darkmoon run --scope identity
→AS-REP roast · 3 accounts
→Kerberoast · svc_sql cracked
→NTLM relay → DCSync
✓Domain Admin, proven

Trigger on any event

Kick off a pentest from a schedule, a webhook, a deploy notification or any other n8n trigger, then fan the results out to Slack, a ticket, or an email.

02
FindingsCVSS
SQL injection9.8
SSRF to metadata9.1
Broken access control8.7
JWT signature bypass7.5
Path traversal6.9

Findings as structured data

Pull findings back into the workflow as data you can filter, threshold and route, so a critical finding can page someone while a low one just files a ticket.

03
Attack surfaceexposure

Fix PRs in the loop (Pro)

Review the pull requests the paid Pro remediation engine prepares from inside your automation, and hand them to the right reviewer.

S.05Start here
The pieces that matter to you

S.06Next
Make the pentest a step in your flow

Darkmoon is open source (GPL-3.0) and self hosted. The n8n node is a community package on npm.