Cyber emergency

We just got hacked. Now what?

Call us now07 3114 2808

Our engineers answer in business hours, Monday to Friday. After hours, Chip, our AI receptionist, answers and logs the request, and the on-call engineer is called for urgent P0 and P1 issues, best effort. Security monitoring runs 24/7.

Not a client yet? After hours, the on-call engineer covers our clients' urgent issues only. Chip takes your details and one of our engineers calls you back in business hours. If something is happening now, call the Australian Cyber Security Hotline on 1300 CYBER1 (1300 292 371), which runs 24/7.

Call us first, then work down the list. The first hour is about stopping the damage and keeping the evidence. You don't have to fix everything at once, and you don't have to do it alone.

Australian Cyber Security Hotline, 24/7: 1300 CYBER1 (1300 292 371).1

Already a client? Say it's a security incident when you call, or log it in your portal.

Get the steps for what you're seeing

The first five minutes

  1. If money has moved, call your bank's fraud line first. Use the number on the bank's website or app, never one from an email.
  2. Call us on 07 3114 2808.
  3. Unplug affected computers from the network, or turn off their wifi. Leave them switched on.
  4. Don't delete anything, and don't reply to or pay the attacker.
  5. Tell your cyber insurer early, if you have a policy.
  6. Write down what you saw and when, on paper or a phone that isn't affected.
Print this card and keep it by the phone.

Your first hour, step by step

Pick what you're seeing. You get your steps in order, and what our engineers do alongside you.

What are you seeing?

Illustrative scenario, based on situations we see often. Not a single client.

A payment went to the wrong account

An invoice with new bank details was paid, or a supplier rings to say they never sent that email.

You, now

  1. Call your bank's fraud line now and ask for a recall. Minutes matter. Use the number on the bank's website or app.

  2. Hold any other payment to that payee, and any bank detail change, until it's checked by phone on a number you already had.

  3. Call us on 07 3114 2808.

  4. Tell your cyber insurer early, if you have a policy.

  5. Write down the amount, date and time, the receiving bank and the payment reference.

Our engineers, alongside you

  • Lock the mailbox that sent or received the fake request and sign it out of every session.
  • Save the sign-in and mailbox logs before anything is changed, so the evidence survives.
  • Find and remove hidden inbox rules and forwarding the attacker left behind.
  • Find who else got the fake email, inside your business and out.

Please don't

  • Don't email the supplier or the bank from the affected mailbox.
  • Don't delete the fake email or the sent items.

Payment redirection scams, also called business email compromise, cost $166.8 million in reported losses in 2025, up 9.3% on 2024.3

Contain first, keep the evidence, then fix. In that order.

See who you have to tell, and by when

Who you have to tell, and by when

Three questions show which reports apply to you. This is general information, not legal advice, and we help you work through it.

Could personal information be involved?

Names with contact details, tax file numbers, health or bank details of staff or customers.

Is your annual turnover over $3 million?
Has a ransom been paid?

Your answers stay in your browser. Nothing is saved or sent.

Who you tell

  1. NowYour bank, if money moved

    Call the fraud line straight away and ask for a recall.

  2. NowYour cyber insurer

    Check your cyber policy and tell your insurer early. Many policies ask for prompt notice.

  3. As soon as you canASD, through ReportCyber

    Report it at cyber.gov.au, or call the Australian Cyber Security Hotline on 1300 CYBER1 (1300 292 371), 24/7.1 It's how ASD warns others. We can help you fill it in.

  4. Within 30 daysAssess whether it's an eligible data breach

    You have 30 days to assess a suspected eligible data breach.8 If it is one, tell the people at risk of serious harm promptly and notify the OAIC with its online form.9

  5. If it changesNo ransom paid

    No payment, no payment report. If a payment is ever made, the 72 hour clock starts then.6

Responsible entities for critical infrastructure assets must report a ransom payment whatever their turnover.6

With the starting answers (personal information not sure yet, turnover not sure, no ransom paid), you tell your bank if money moved, your insurer and ASD now, and assess within 30 days whether it's an eligible data breach.

The OAIC received 1,205 data breach notifications in 2025, the most in a year since the scheme began.10

Read more on ransomware payment reporting

After the first hour: how we get you back

Every incident runs in the same order, whether it's one mailbox or a whole office. How long each stage takes depends on what we find, and we tell you as we go.

  1. First hours

    Contain

    Stop it spreading: affected accounts blocked and signed out, affected computers cut off from the network, any suspicious payment chased with your bank. Evidence saved before anything is changed.

    What we need from you: Someone who can approve actions, and admin access to Microsoft 365 or a person who can grant it.

  2. First days

    Find out what happened

    Sign-in logs, mailbox rules, computer alerts and backups checked, so we know how they got in, what they touched and whether they're still there.

    What we need from you: Your notes of what people saw, and when.

  3. When it's clean

    Recover

    Systems and data come back in the order we agree with you, from backups we've checked are clean. A person opens the restored data to check it before staff go back to work.

    What we need from you: Which systems matter most to keep the business running.

  4. After

    Report and close the gap

    A written account of what happened, what was touched and what we did, for your insurer, a breach assessment or the board. Then we fix how they got in.

    What we need from you: Time with us to agree the fixes, and your yes before any project work starts.

Read our incident response playbook

Client or not, here's how the call goes

What happens next depends on whether we already look after you. Pick the one that fits.

It's 2am and something's wrong.

Illustrative scenario, based on situations we see often. Not a single client.

Your computers and Microsoft 365 accounts are watched 24/7 by Guardz with SentinelOne. If an analyst confirms an attack, the account is suspended or the computer cut off, inside the response rules we agreed with you at setup. If it's contained overnight, one of our engineers calls you at the start of business.

You get a written account of what happened, what was touched and what we did.

What we do

  • Call 07 3114 2808 or log it in your portal, and say it's a security incident.
  • Our engineers already know your setup and have the access they need.
  • We handle the evidence your insurer or a breach assessment will ask for.
See how 24/7 monitoring works

How security analysts act on an alert, inside response rules each client sets: Guardz MDR services.12

Who picks up when you call

When you call
Our engineers answer in business hours, Monday to Friday. After hours, Chip, our AI receptionist, answers and logs the request, and the on-call engineer is called for urgent P0 and P1 issues, best effort. Security monitoring runs 24/7.
Not a client yet, after hours
Not a client yet? After hours, the on-call engineer covers our clients' urgent issues only. Chip takes your details and one of our engineers calls you back in business hours. If something is happening now, call the Australian Cyber Security Hotline on 1300 CYBER1 (1300 292 371), which runs 24/7.
Response targets for clients
On Advantage, Ultimate and RealBytes One, in business hours: P0 within 1 hour, P1 within 2 hours, P2 within 4 business hours. After hours is best effort.
How fast we actually answer
Measured on our service desk from 24 August to 22 November 2026: a median first response of 32 minutes in business hours, across 1,041 client tickets.
Chip, the Real Bytes AI receptionist, drawn as a friendly robotChip is our AI assistant. Our people are the ones who fix things.

The people behind the phone

  • Philip Verner, Director at Real BytesPhilip VernerDirector
  • Blake Bath, General Manager at Real BytesBlake BathGeneral Manager
  • Mason Wise, MSP Practice Lead at Real BytesMason WiseMSP Practice Lead
  • Mitchell Morgan, Automation & Platform Lead at Real BytesMitchell MorganAutomation & Platform Lead
  • Travis Jacob, Operations Manager at Real BytesTravis JacobOperations Manager
  • Bill Nobbs-O'Brien, Service Desk & Field Engineer at Real BytesBill Nobbs-O'BrienService Desk & Field Engineer

Photos: Real Bytes. Meet our engineers

Check us before you trust us

It's fair to want to know who you're letting into your systems. Each of these can be checked.

SMB1001 Diamond
Independently audited by BSI. Check our certificate on CyberCert Verify.
ASD Network Partner
A partner in ASD's Cyber Security Partnership Program.
4.8 from 40+
Google reviews. Read what clients say.
Since 2013
In business since 2013. Real Bytes as it is today formed in 2017.

What we can't promise, and what we need from you

Straight answers matter most on a bad day.

What we can't promise

  • That every file comes back. Clean backups make recovery likely; without them, options shrink.
  • That money already paid comes back. Only your bank can try a recall, and speed matters.
  • Legal advice. We help you work through the reporting rules, and we tell you when to call a lawyer.

What we need from you

  • Someone who can make decisions, on the phone, for the first hour.
  • Admin access to Microsoft 365 and the affected computers, or a person who can grant it.
  • Your cyber insurance policy details, if you have one.
  • Your notes: what people saw, and when.

Questions people ask in the middle of an incident

Should we pay the ransom?

The Australian Government does not condone paying ransoms to cybercriminals.11 Paying doesn't guarantee your files come back, or that stolen data is deleted. Don't contact or pay the attackers without advice from us and your insurer. If a payment is made, a business with turnover over $3 million must report it to ASD within 72 hours.67

Should we change all our passwords right now?

Not from a computer that might be infected, and not one at a time on your own. Call us first. We save the sign-in logs, then reset the password and sign the account out of every session in one go, from a clean device, so the attacker loses access in one move.

When do we tell our cyber insurer?

Early. Check your cyber policy and notify your insurer early, alongside calling us to contain it. Many policies ask for prompt notice, and some have their own response team. Your policy wording says what they need from you.

Do we have to report this to the OAIC?

Only if it's an eligible data breach: personal information lost or accessed without permission, likely to cause serious harm, at a business the Privacy Act covers. You have 30 days to assess a suspected breach.8 If it's eligible, tell the people at risk promptly and notify the OAIC with its online form.9 Most businesses with turnover of $3 million or less are exempt, with exceptions such as health service providers.8

Should we report it to ASD?

Yes, we recommend it. Report it through ReportCyber on cyber.gov.au, or call the Australian Cyber Security Hotline on 1300 CYBER1 (1300 292 371), which runs 24/7.1 Reports help ASD warn other businesses. If your identity or your staff's details were taken, IDCARE (1800 595 160) can help too.1

We're not a Real Bytes client. Will you help?

Call us on 07 3114 2808 in business hours, Monday to Friday. After hours, the on-call engineer covers our clients' urgent issues only, so Chip takes your details and one of our engineers calls you back in business hours. If something is happening now, call the Australian Cyber Security Hotline on 1300 CYBER1 (1300 292 371), which runs 24/7.1 We tell you on the call whether we can take it on and how the work is charged, before we start. Nothing goes ahead without your yes.

How much does incident response cost?

If you're on a Real Bytes plan, 24/7 monitoring and the investigation of every incident are part of your plan, as our Pricing page sets out. Recovery work beyond that, and work for businesses that aren't clients, is agreed with you before it starts.

What if it turns out to be nothing?

Then we tell you plainly and you get back to your day. We'd much rather hear about a false alarm than a real attack a day late.

Once it's calm, let's stop it happening again

When the incident is closed, a free 30 minute chat with a senior engineer goes through how they got in and what would stop the next one. No slide deck, and you leave with at least one thing you can fix yourself.

Three months, then month to month on 60 days' notice. No exit fees. Onboarding is quoted before you commit.

Already a client? Log a job in your portal or email helpdesk@realbytes.com.au.

What happens next

  1. You pick a time that suits you.
  2. One of our engineers calls you. It takes 30 minutes and it's free. There's no slide deck.
  3. If we can help, we send a written plan. If we can't, we'll tell you who can.
  4. Nothing happens until you say yes.

Sources

Figures and sources checked 22 November 2026. The small numbers on this page link here.

  1. Queensland Government, Report a cybercrime. Australian Cyber Security Hotline 1300 CYBER1 (1300 292 371), ReportCyber and IDCARE. Page last modified 13 August 2024, read 22 November 2026
  2. Australian Signals Directorate, ReportCyber. cyber.gov.au, the Australian Government's place to report a cybercrime or cyber security incident
  3. ACCC National Anti-Scam Centre, Targeting Scams 2025. ACCC, March 2026. Payment redirection losses, table 3
  4. BizCover, Australia's latest cyber threat report: what small businesses need to know. An insurer's summary of ASD's Annual Cyber Threat Report 2025-26, 12 November 2026. A secondary source
  5. Australian Government, business.gov.au: Annual Cyber Threat Report 2025-26. Summarising ASD's Annual Cyber Threat Report 2025-26, 28 October 2026
  6. Department of Home Affairs, Ransomware payment reporting factsheet. Who must report, the 72 hour window, ASD's reporting form and the penalty. In force from 30 May 2025, read 22 November 2026
  7. Federal Register of Legislation, Cyber Security (Ransomware Payment Reporting) Rules 2025. Section 6: the $3 million turnover threshold
  8. Federal Register of Legislation, Privacy Act 1988. Section 26WH (assess within 30 days) and section 6D (small business exemption and its exceptions). Compilation of 4 June 2026
  9. OAIC, Report a data breach. Notify individuals at risk of serious harm promptly, and notify the OAIC with its online form. Read 22 November 2026
  10. OAIC, Data breach notifications increase to all time high in 2025. Notifiable Data Breaches statistics, calendar year 2025, published 6 July 2026
  11. Department of Home Affairs, Ransomware Action Plan. October 2021: "The Australian Government does not condone the payment of ransoms to cybercriminals."
  12. Guardz, MDR services. Guardz support article: analysts, response actions and customer-defined response policies, read 22 November 2026