AI agents investigate every alert, add context, and prepare cases for response, on a full-stack SecOps platform that captures and correlates all your security data.
Cloud-based SIEM platform providing visibility across all your data sources
Every alert investigated, with a verdict and the evidence behind it
Manage your external footprint, publicly available data, and Dark Web leaks
Log management and threat detection across any of your log sources
Get ultimate assurance that your environment is free from threat actors
Fully featured distrubuted NDR for on-premises and public cloud environments
A SecOps platform purpose-built for industrial and OT environments
Integrated endpoint agent providing deep visibility, response and forensics
Deploy honeypots and honeytokens and stay ahead of threat actors
24x7 security operations from our Australian SOC. AI investigates every alert, and experienced analysts validate findings and contain threats around the clock.
24x7 managed detection and response across endpoint, network, cloud, identity, and log sources
AI investigations and 24x7 MDR on the Microsoft Sentinel you already own
Eyes-on-glass SOC and continuous threat hunting
Expert hunters and AI agents find attacker activity your alerts missed
Quickly recover from cyber attacks and breaches
ThreatDefence is the only SecOps as a Service company providing broad coverage across your entire technology stack with evidence-based security.
We provide security teams with full-stack SecOps infrastructure – you get deep visibility from day one, gain control over your security data, and get access to a comprehensive set of ready-to-use tools, detections, workflows, playbooks and scenarios.
24x7 SOC, Continuous Monitoring, Threat Containment and Incident Response
Visibility and actionable insights for all IT assets
Leverage our Cyber Range to train defenders based on real-world scenarios and simulations
OT and industrial cyber security services for critical infrastructure
Monitoring, evidence and a 24×7 SOC in one platform
Compliance monitoring, evidence and board reporting
Privacy Act reform impacts, obligations, and practical security considerations
Monitoring and compliance support for critical infrastructure environments
A practical guide to securing critical infrastructure with continuous monitoring
A practical buyer’s guide for schools evaluating SIEM and SOC services
A practical guide to selecting the right SIEM and SOC service for local government
Articles on security operations, AI and compliance
Events, awards and company news
Read what our customers say about us
Solution briefs and datasheets
How we keep your data secure
Technical support and knowledge base
Guides, case studies, and advisories in one place
How AI agents investigate alerts and run security operations
Free ebook: a practical guide to adopting an AI SOC platform
A practical guide to incident response and digital forensics
Where SOAR playbooks fit and where AI agents take over
Free ebook: modern security operations with Microsoft Sentinel
How the framework is structured and what changes from the Essential Eight
How an attack unfolds stage by stage and how to detect each one
November 18, 2026
November 16, 2026
November 13, 2026
We provide end-to-end SecOps solutions for Managed Security Service Providers (MSSPs), Managed Service Providers (MSPs), and Value-Added Resellers (VARs).
Find out how you can become a ThreatDefence partner.
Protect your entire technology stack and build your SecOps on your own pace
White-labeled AI SOC for every client tenant, co-managed with our SOC team
Launch your SOC business without any upfront investment
Embed security operations, threat intelligence and exposure data in your product
Sovereign SOC for Australian MSPs and MSSPs, with onshore analysts and client data
Set the rules for closing alerts automatically, with evidence checks and review
How MSPs deliver branded security monitoring with a SOC partner
ThreatDefence was an official partner of the Cyber Resilience Summit NSW, 29 October 2026 at Hilton Sydney.
Our team was back at BSides Canberra, and our cyber quiz was a hit again.
Two days in Perth with our partner Ever Nimble, on security operations and cyber resilience.
Sponsors of the AUSCERT Cyber Security Conference on the Gold Coast.
Sponsors of the Gartner Security & Risk Management Summit in March.
Sponsors of the Cyber Security for Critical Assets Summit in Perth, February 2026.
Expert conversations with speakers and attendees at CyberCon Melbourne 2025.
An infostealer is malware that copies credentials and session data from an infected device and sends them to an attacker. One infection can expose every password saved in the browser, along with the signed-in sessions that let an attacker skip multi-factor authentication.What the attacker receives is called a stealer log. This guide opens one up, shows how its contents turn into an intrusion, and sets out which credentials to deal with first.
A stealer log is a folder of files taken from one device. Each part answers a different question for the criminal who buys it.
The malware runs for seconds. It collects, uploads, and in many cases removes itself. The user notices nothing, and by the time anyone looks there may be no file left to find.
The log is more dangerous than a list of leaked passwords. The site address is recorded with each credential, so the buyer knows exactly where it works. The cookies are current, so a session can be resumed before the password is ever needed.
Infostealers are a product. The people who write them do not usually infect anyone, and the people who use the stolen data did not usually steal it. Each step is a separate trade.
They write and maintain the malware and rent it out by subscription. Customers receive a builder, a control panel, and regular updates that keep pace with browser changes and security software.
They rent the malware and spread it through search ads for fake software, poisoned downloads, links in video descriptions and forums, and fake verification pages. They are paid by the volume and quality of logs they bring in.
They run the markets and subscription channels where logs are sold. A buyer can search millions of logs for a company’s domain or a specific web address.
They buy logs in bulk, test the corporate credentials in them, and resell working access with a description of the victim.
These are ransomware affiliates, fraud groups, and intruders looking for a first foothold.
The economics explain the scale. A subscription costs little, distribution is automated, and one infected computer yields hundreds of credentials. Individual logs sell cheaply because there are so many. The value is extracted later, by whoever finds a corporate login among the personal ones.
The 2022 breach of the Australian health insurer Medibank shows the full path from one saved password to a national incident.
In civil penalty proceedings filed in June 2024, the Office of the Australian Information Commissioner alleges that the breach began with the credentials of a contractor who worked on the IT service desk. According to the allegations, the contractor had saved work credentials in a personal browser profile, the profile synchronized them to a home computer, and malware on that home computer stole them.
The regulator further alleges that the attacker used those credentials to sign in to the company’s VPN, which did not require multi-factor authentication, and went on to take approximately 520 gigabytes of data. The proceedings concern the personal information of 9.7 million people. The case is before the Federal Court, and the allegations have not been decided.
Whatever the court finds, the sequence alleged is the standard infostealer intrusion:
No part of it involved an attack on the company’s own computers until the attacker signed in. Every step in the sequence has a control that would have broken the chain, and the Reduce the Risk section sets them out.
Infostealers are simple programs, and their simplicity is part of why they succeed.
A browser’s saved passwords and cookies belong to the user. Any program the user runs can reach them. The malware never needs administrator rights.
A typical stealer installs no service and leaves nothing running, so a scan the next day finds a clean machine. Some arrive with a loader that stays behind and fetches more malware, which is why an infected device is untrusted until it is rebuilt.
The victim opens the file deliberately, believing it is an installer, a game modification, or a document. Some campaigns ask the user to paste a command to complete a fake verification step, which sidesteps download protections entirely.
Each customer receives a freshly built and packed copy, so file signatures are of limited use.
Browsers encrypt saved data and keep adding safeguards. Stealer developers publish workarounds within weeks, because their business depends on it.
The home computer, the family laptop, and the contractor’s own machine have consumer antivirus at best.
The practical conclusion is that prevention on the endpoint will never be complete. The dependable defenses are the ones that make stolen data less useful: sessions that expire quickly, tokens bound to a device, and access that requires a managed machine.
The trades described earlier work in sequence, and the gaps between the steps are where a defender has time.
The timing depends on what was stolen. Cookies are tried within hours, while the sessions are still valid. Passwords circulate for weeks or months and are tried long after the infection was cleaned up. An exposure alert that arrives days after the infection is late for the sessions and early for the passwords, and both need action the day it arrives.
The system information in the log identifies the infected machine, which decides how the organization can respond.
The computer name matches the organization’s naming scheme, so the security team can isolate it, collect evidence, and reimage it.
The computer name is a home or default name, and the installed software includes games or consumer applications. The organization has no agent on it and no authority over it. The work credentials were there because the user signed in to work systems from home.
The username and installed software point to another company. The credentials are for the organization’s systems, and the cleanup belongs to someone else.
Exposure alerts for personal and contractor devices arrive with nothing from the organization’s own endpoint protection, because that protection was never on the device.
Where the infected computer is one the organization manages, endpoint telemetry can show the theft as it happens. The behaviors are distinctive.
Browsers store saved logins and cookies in known files inside the user’s profile. A process other than the browser opening them, particularly for several browsers in a row, is the core signal.
A newly downloaded program, or one unpacked from an archive, runs within minutes of arriving.
PowerShell or a similar tool is launched by the user with a long encoded command, immediately after browsing.
The collected data is usually compressed before it is sent.
A single upload goes to a host nothing else in the organization contacts, sometimes to a messaging platform’s interface.
This is part of the standard collection routine.
The file removes itself shortly after first running.
Detection that waits for a human to read an alert will usually be reviewing history, which is still valuable. It identifies the device, the time, and the user, and starts the response before the log is sold.
When a managed device is confirmed infected, treat every credential the user had saved as stolen, even if no exposure alert has arrived yet.
A single log can list hundreds of credentials. Deal with them in order of the access they give.
An exposure alert usually reports only the entries that matched the organization’s domain. The same log holds the user’s logins for suppliers, cloud consoles, and personal accounts, and those are equally known to the buyer.
The order matters. A new password typed on a device that still carries malware goes straight to the attacker.
The account takeover guide explains the account steps, and the session hijacking guide shows what each action ends.
The infection date in the log sets the start of the period to review. For each exposed account, look for the following.
An existing session shows activity from an address the user has never used, with no sign-in recorded there.
Successful sign-ins arrive from hosting providers or other countries, or attempts are stopped by the second factor.
VPN or remote desktop sessions come from unfamiliar addresses.
New authentication methods, registered devices, application grants, or mailbox rules appear.
New accounts, role changes, or configuration changes are made with the exposed account.
The same download source or file turns up elsewhere in the fleet.
Where any of these appear, the incident is an account takeover or a network intrusion and should be handled as one.
Most infostealer exposure comes from devices the organization does not manage. A clear position on personal devices does more than any amount of endpoint tooling on the corporate fleet.
The workable positions, in order of strictness, are these.
Whichever is chosen, a few rules help.
Tell staff never to save them there, and never to sign a personal browser profile in on a work computer. Browser synchronization quietly copies saved passwords to every device using that profile.
Their staff sign in to the organization’s systems from devices nobody has assessed. Contract terms can require managed devices or restricted access.
Staff should know that a personal device found infected has to be cleaned before it is used for work again, and who will help them do it.
The first controls here follow the sequence in the documented case. The rest limit what a stolen log is worth.
Provide a managed password manager, and switch off the browser’s own password store through browser policy on work devices.
Browser policy on work computers blocks sign-in to personal profiles, so saved work passwords are not copied to a home device.
A VPN, remote desktop gateway, or support tool that accepts a password alone turns one saved password into network access.
A passkey gives a stealer no password to copy.
Token protection and compliant-device policies stop a stolen cookie or token being used from another machine.
A stolen cookie for an admin console should expire in hours.
Restrict what users can install and which browser extensions are allowed.
Watch stealer logs and breach data for the organization’s domains, and treat each alert as an incident with a deadline.
The browser and installation controls reach only managed computers, which is why the position taken on personal devices matters as much as any setting in this list.
ThreatDefence monitors leaked and exposed credentials for customer domains. When staff logins appear in stolen data, our analysts turn the exposure into a prioritized list of password resets and session revocations, and check sign-in records for use of the stolen access.
Our endpoint agent collects forensic evidence from an infected device, and our SOC can revoke sessions and disable accounts under agreed authority. Our security advisories track current campaigns, including infostealers and session theft.
Experiencing a breach?
Our incident response team answers 24x7, with or without a retainer.
Explore Identity Threat Detection and Response
Ask about credential exposure monitoring and a free Microsoft 365 forensic review for your organization.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
An infostealer is malware built to copy credentials from a computer and leave. In seconds it collects the passwords and cookies saved in every browser, autofill data, files from common folders, and logins stored by VPN and remote access clients, then uploads them as one package. It is rented as a subscription service, and well-known families include Lumma, RedLine, and Vidar.
A stealer log is the package one infection produces: a folder for one device holding its saved passwords with the site each belongs to, browser cookies, autofill data, system details, a screenshot, and selected files. Logs are sold singly or by subscription, and buyers search them by web address. One log commonly holds hundreds of logins, most of them personal and a few of them corporate.
Yes, through the cookies. A session cookie is issued after the user has passed the second factor, and a service that receives the cookie from another browser treats the session as already authenticated. The stolen password alone is still stopped by MFA. For an exposed single sign-on account the sessions have to be revoked as well as the password reset, and short session lifetimes and device binding limit what a stolen cookie is worth.
No. The log also holds live session cookies, which on many services keep working after a password change until the sessions are revoked, and it may hold API keys, SSH keys, and tokens stored on the device. A new password typed on the infected device can be stolen again. Reset from a clean device, revoke sessions, rotate the other secrets, and rebuild the computer before it is used for work.
Credential exposure monitoring searches stealer logs and breach data for the organization’s email domains and for the web addresses of its sign-in pages, VPN, and admin consoles. Searching by address matters, because it finds contractors and personal accounts that sign in to company systems. National cyber agencies also notify organizations of exposures they come across, and Microsoft Entra ID flags users whose credentials appear in leaks.
Treat every work login saved on it as stolen. Have the employee stop using the device for work, reset their work passwords from a clean device, revoke their sessions, and review the accounts for sign-ins since the infection date. The organization cannot examine or reimage a personal computer, so the condition for using it again is a clean reinstall, and the employee needs help changing their personal passwords too.
A breach list comes from one compromised service and holds that service’s usernames and passwords, often hashed and often years old. A stealer log comes from one person’s computer and holds their logins for every service, in clear text, with the exact sign-in address and current session cookies. A breach list feeds credential stuffing. A stealer log gives direct, targeted access.
Often. Access brokers buy logs, test the VPN, remote desktop, and administrator logins in them, and sell working access to ransomware affiliates. The Australian Signals Directorate has warned that stealer infections on personal devices are being used to compromise corporate networks. A remote access service that accepts a password alone is the usual way in, and the gap between the sale of the log and the intrusion can be days or months.
Session Hijacking and Token Theft
Account Takeover, Followed Through the Logs
Password Spraying and Credential Stuffing