Audit NBD-related services and kernel modules – Ensure that all NBD-related drivers are loaded correctly and that any relevant startup or shutdown scripts haven't been altered.
Validate disk templates and partition schemes – Re-check whether templates used to deploy new VPS are intact, especially after the breach. Templates might need to be re-imported or rebuilt.
Inspect Virtualizor logs and recovery points – Review logs for anomalies and restore from a known-good backup if available.
Engage Virtualizor support – If the root cause traces back to Virtualizor updates or corrupted internal logic after the breach, official support may be required to resolve it.