Fix the weak spots.
Keep the site you built.
Vulnerable plugins, malicious code, and careful repairs. We’re building protection that checks the fix before it reaches your live site.
Get early access
We’ll let you know when it’s ready.
We’ll email when access opens, with setup details.
No launch date announced yet.
Product concept for the upcoming WordPress integration. Illustrative preview with sample data.
The fix matters. So does the rest of your site.
We’re building protection that understands the plugins, themes, and everyday flows your WordPress site depends on.
Find the weak plugin. Choose the right fix.
Identify vulnerable components and work out whether to patch, update, or remove them. Check dependencies before changing what the site relies on.
- Vulnerable or abandoned plugins and themes
- A patch or supported update where available
- Removal plans that account for site dependencies
A plugin needs a security update.
wp-content/plugins/harbor-forms/- Before
- A vulnerable installed version
- Observed
- A supported patch is available
Test the update and the form it powers before publishing the change.
Illustrative example · Synthetic dataRemove the bad code. Keep the good work.
Find injected scripts, backdoors, and altered files. Restore clean components while preserving the content and customizations that belong on your site.
- Injected code and malicious redirects
- Backdoors and unexpected file changes
- Clean restore points for affected components
A theme file contains injected code.
wp-content/themes/harbor/footer.php- Before
- Your approved theme file
- Observed
- An unfamiliar script was added
Remove the injection in a safe copy, then compare the repaired page.
Illustrative example · Synthetic dataA patched site still needs to work.
Check the pages, forms, and store flows affected by a repair. Publish a verified change, with the previous version ready to restore.
- Restore points before supported changes
- Page, form, and WooCommerce flow checks
- Rollback when validation fails
The patch passed its site checks.
Repair checks / Harbor Forms- Before
- Restore point saved
- Observed
- Homepage and form checks passed
Publish the verified patch and keep monitoring the repaired component.
Illustrative example · Synthetic dataSafe repair
Don’t trade a security problem
for a broken website.
Patch a vulnerable component. Remove malicious code. Check the dependencies and test the pages people use before publishing the repair.
A vulnerable plugin. A working site.
wp-content/plugins/harbor-forms/Save a restore point
Keep the current files and configuration.
Test the repair
Apply the supported patch in a safe copy.
Check the important flows
Verify pages, forms, and checkout.
Publish and keep watch
Keep rollback available after the repair.
Interactive example. No live site is changed.
Yes, that includes your store.
WooCommerce protection is part of the plan. A plugin repair should account for product pages, cart, and checkout, too.
Keep the site you worked hard to build.
Be first to hear when WordPress protection is ready.
Join early accessBefore you
get started.
A few details about the repair workflow.
Is WordPress protection available yet?
The WordPress product is coming soon. Join early access to hear when the repair workflow is ready. The product views on this page show the planned experience.
Will you just delete a vulnerable plugin?
Removal is not the first move when a plugin powers something important. The workflow checks dependencies, looks for a supported patch or update, and tests the result. Unsupported or uncertain changes need your review.
How do you keep a repair from breaking the site?
Save a restore point, test in a safe copy, and check the affected pages and flows before publishing. If validation fails, keep or restore the previous state. Compatibility and supported hosting setups will be confirmed during early access.
Does this include WooCommerce stores?
WooCommerce is part of the planned WordPress coverage. Repairs should account for product pages, forms, cart, and checkout behavior. Payment providers and unrelated systems remain outside the authorized scope.
Is this a hosting service?
No. rootscan is being built as a security and repair service alongside your hosting, backups, and maintenance. Connection requirements will be shared before access opens.
Can it remove existing malware?
Malware cleanup and repairing affected components are part of the planned workflow. The connection needs enough authorized access to inspect and restore files, and the result needs validation.
Running your store on Shopify?
Continuous protection for your storefront, apps, and connections.