> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/prevention-tools/credentials/infected-devices.md).
# Infected devices
An Infected Device alert means one of your employee devices has been identified as compromised by infostealer malware, by Hudson Rock or Flare. The device is actively exfiltrating data (passwords, cookies, browser autofill, saved credentials) until it is fully wiped.
## Resolving an alert
1. Isolate the device from the network immediately (disconnect from Wi-Fi and LAN).
2. Wipe and reinstall the device from scratch. A virus scan alone is not sufficient.
3. Force a password reset for all accounts used on that device.
4. Invalidate active sessions on those accounts (sign out everywhere) to neutralise any stolen session cookies.
5. Enable MFA on the affected accounts.
## Personal devices
Stoïk detects infected devices based on professional account activity. It cannot determine whether the device itself is a company-issued machine or a personal one. A personal device (a phone or laptop on which an employee connected a professional account) can therefore appear as an Infected Device alert. If you identify an alert as relating to a personal device, update the device type from the alert side panel:
1. Open the alert.
2. Switch the **Device type** from *Professional* to *Personal*.
The alert moves to **Dismissed** status. It remains visible in the list but is filtered out by default and no longer counts as an active alert.
{% hint style="info" %}
Even on a personal device, the professional accounts used on it remain at risk. Before dismissing the alert, make sure the employee has reset their passwords and invalidated active sessions for any professional account they accessed on that device.
{% endhint %}
{% hint style="warning" %}
If you believe an alert is a false positive, you can request a discard directly from the side panel. Stoïk will review the request before closing it.
{% endhint %}
## Troubleshooting
There is no device name, or I don't recognise the device
The alert is real: the malware didn't capture those details, or the host name it reported means nothing (for example "PRIVAT"). A device you don't recognise is usually a personal one where an employee used a work account: use the username or email in the leaked data to find them.
Stoïk doesn't tell personal and work devices apart: you change the device type yourself, see [Personal devices](#personal-devices). If the alert shows no user at all, contact : the log often holds a username that Stoïk Protect doesn't display.
The device was cleaned long ago
Providers buy stealer logs as snapshots, so they can't know when a device was wiped. An infected device is archived automatically 180 days after its last leak. For many old devices at once, contact : the CERT can close them in bulk as patched.
I had an infection years ago and don't see it
Providers keep everything they collect, but they focus on recent leaks: an old infection may never show up.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.stoik.io/prevention-tools/credentials/infected-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.