Backups, ransomware and AI threats on Australian hosting

Attackers use AI to write more convincing phishing, faster. The defence has not changed: patch what you run, give every account the least access it needs, and keep daily backups you have actually restored once. Every Vioflare plan includes daily backups on Melbourne infrastructure.

Key takeaways

  • AI changes the volume and polish of attacks, not the recovery plan.
  • Daily backups are the recovery layer; they are not a substitute for updates.
  • A backup on the same disk as the live site is not a backup against ransomware.
  • Test one restore after go-live, and again after any major change.
  • An AI coding agent with deploy access is a new, real way to lose a database.

What to require from any Australian host

  • Automated daily backups with a retention window you can state out loud.
  • Storage separate from the live disk, so encrypting public_html does not encrypt the copies.
  • A restore path that covers files and the database, since half a restore is an outage with extra steps.
  • TLS on every admin surface — panel, webmail, database tools.
  • Support that can help with a cleanup, in your timezone. Vioflare support is Australian-based.

All of this is included across the hosting range, and the about page covers how the infrastructure is run.

What AI has actually changed

Be precise about this, because the hype is unhelpful:

  • Phishing quality is up. Grammatically perfect, contextually specific messages are now cheap to produce. Staff training that relied on spotting bad English no longer works.
  • Vulnerability discovery is faster. The window between a plugin disclosure and exploitation attempts in the wild is shorter than it was.
  • Automated agents now have credentials. A coding assistant with deploy or database access can drop a table or overwrite a directory in one step, with no malice involved.

What has not changed: the fix is still patching, least privilege, and restorable backups.

The failure modes backups actually cover

  • Ransomware that encrypts the document root.
  • A compromised plugin or dependency that injects code you then have to unpick.
  • An accidental deletion — by a person, a script, or an AI agent with more access than it needed.
  • A bad deploy that works on your machine and breaks in production.

In each case the question is not "do we have backups" but "when did we last prove we can restore one". Those are different questions and only the second one matters at 11pm.

Practical hardening, in priority order

  1. Update the application, its dependencies and its plugins on a schedule you actually keep.
  2. Remove accounts and API keys that are no longer used — especially keys issued to tools you have stopped using.
  3. Give every integration the narrowest permission that works. A deploy token does not need database superuser rights.
  4. Enforce HTTPS everywhere, with free SSL on every hostname including admin panels.
  5. Restore a backup into a staging location and confirm the site comes up.
  6. Keep an inventory of which external services hold credentials to your site.

Where AI agents need a boundary

If you let an assistant deploy, give it its own credentials, scoped narrowly, and keep the database behind a separate account. Two reasons: you can revoke it independently, and the audit trail tells you what the agent did rather than what "the team" did. This is the same reasoning you would apply to a contractor, applied to a tool.

Frequently Asked Questions

Are backups a substitute for security updates?

No. Backups are the recovery layer for when prevention fails. An unpatched application will simply be compromised again after you restore it.

How often should I test a restore?

At least once after go-live, then after any major application change or migration. An untested backup is an assumption, not a safeguard.

Does Vioflare hosting include backups?

Yes, daily backups are included across the hosting range on Melbourne infrastructure. Check your plan's details on the hosting pages for the retention that applies.

What should I do first if my site is compromised?

Take it offline or into maintenance, change the credentials that could have been used, then restore from a backup taken before the compromise — and patch the entry point before putting it back up.

Can an AI coding assistant delete my data?

Yes, if you give it write access to production. Scope its credentials narrowly, keep database access separate, and rely on your daily backups as the recovery path.