A laptop displays a security alert and ongoing offline scan beside a phone showing account security settings.
A report linking orexports.com to files tagged GuLoader and AgentTesla raises two separate questions for Windows users: did malware actually run, and could it have exposed their accounts? Seeing the domain in a blocked connection is not enough to establish infection. For a credible compromise, however, the response needs to cover both account recovery and Windows cleanup—not just a reassuring antivirus result.

A laptop displays a security alert and ongoing offline scan beside a phone showing account security settings. What the orexports.com report establishes​

According to 2-Spyware, its copy of abuse.ch URLhaus data contained 10 file URLs added on November 4, 2026, between approximately 09:28 and 11:31 UTC. Nine carried a GuLoader tag and eight an AgentTesla tag. All ten were marked offline when the publication reviewed that data.

Those are tracker classifications, not independently confirmed findings about each file. 2-Spyware says it did not download the samples or test its removal procedure on an infected PC. The report therefore does not establish the exact payloads, what information they collected, or where they sent it. Its November 16 homepage request returned an unrelated page, which does not establish that the domain was cleaned or explain who placed the files there.

That evidence warrants caution, not a declaration that every computer encountering the address is infected.

Why the malware names matter​

MITRE ATT&CK describes Agent Tesla as.NET-based spyware with capabilities that include credential theft, keylogging, clipboard collection and screen capture. It also documents persistence through mechanisms such as startup entries and scheduled tasks. These are family-level capabilities, not proof that the files associated with orexports.com performed every listed action.

The practical distinction is between evidence of a connection and evidence of execution. A blocked request alone does not establish that a payload ran; a relevant antivirus detection or an unexpected executable running on the device deserves closer investigation. The domain name is a lead, not a diagnosis.

Recover accounts from another device first​

For credible suspected execution, the recommended response order is to stop using the suspect PC for sensitive activity, disconnect it from the network, and conduct account recovery from another trusted device. This is precautionary containment—not a claim that every password was definitely stolen.

The FTC’s compromised-account guidance supports the following recovery checklist:

  1. Change exposed passwords to unique, strong credentials.
  2. Sign out of the account on all devices. Do not treat a password change as a substitute for this separate step.
  3. Enable two-factor authentication wherever available.
  4. Check recovery details, including the recovery email address and telephone number.
  5. Inspect email forwarding rules and remove unauthorized ones.
  6. Review messages and account activity for actions you did not take.

Prioritize email, then other sensitive accounts used on the suspect PC. For a work or school device, involve IT before resetting it; Microsoft also directs users of managed PCs to their organization’s support team for recovery assistance.

Run Microsoft Defender Offline—with its limits in mind​

Microsoft Defender Offline scans outside the normal Windows environment, making it harder for persistent malware to conceal itself. Microsoft’s Windows Security documentation describes it as a quick scan in Windows Recovery Environment, not a full examination of every file.

There is an important hardware boundary: Microsoft Learn lists support for x64 Windows 11 and x86/x64 Windows 10, but explicitly excludes Windows on Arm and Windows Server. Owners of Arm-based PCs should not assume that these instructions apply.

Start the scan​

On an applicable PC:

  1. Save open files and close applications.
  2. Open Windows Security.
  3. Select Virus & threat protection > Scan options.
  4. Choose Microsoft Defender Antivirus (offline scan), then Scan now.
  5. Approve the prompts and allow the computer to restart.
  6. After Windows returns, open Protection history to review the results.

Microsoft says the offline scan takes approximately 15 minutes. Its prerequisites include local administrator privileges and an enabled Windows Recovery Environment. If the system drive uses BitLocker, Microsoft instructs users to suspend protection before the scan; otherwise, the restart may request the recovery key.

If nothing happens​

Microsoft documents a particularly unhelpful failure mode: when Windows Recovery Environment is disabled, the scan does not run and may display no error.

Open an administrator Command Prompt and check:

reagentc /info

If the status is disabled, Microsoft documents this command to enable it:

reagentc /enable

If enabling it fails, seek technical assistance rather than improvising changes to recovery partitions.

A separate Full scan examines every file and program, according to Microsoft. Neither scan should be interpreted as evidence that previously exposed accounts have been secured; account recovery remains a separate job.

Resetting Windows: useful, but not a magic eraser​

Do not delete unfamiliar scheduled tasks or startup entries merely because their names look strange. MITRE documents these as possible Agent Tesla persistence mechanisms, but that does not make every unfamiliar entry malicious. Investigation should establish what an entry launches before removal.

For readers choosing a reset, Microsoft’s Windows 11 procedure is:

Settings > System > Recovery > Reset PC

The choices have materially different consequences:

  • Keep my files reinstalls Windows while preserving personal files and removing apps and settings.
  • Remove everything removes personal files, apps and settings as well.

Back up essential data and have the BitLocker recovery key available before proceeding.

There is also a stronger recovery path than treating reset as the final word. Microsoft’s malware-recovery guidance recommends a clean installation using installation media if infection problems continue after scanning. That removes Windows, personal files, apps and settings from the selected drive. Installation media can be created on another working PC.

The editorial recommendation for a credible loader-and-stealer compromise is to favor rebuilding a trustworthy system over repeatedly guessing which suspicious entry remains. That is risk-based advice, not a tested removal guarantee for these particular files.

Finish the recovery beyond Windows​

Rebuilding the computer and securing accounts are complementary tasks. Continue reviewing account activity, and use the FTC’s identity-theft recovery service if personal information was stolen; it provides a personalized recovery plan.

The central lesson is straightforward: a domain alert is not proof of infection, and a clean scan is not account recovery. Establish what happened, protect accounts from a trusted device, and choose a Windows recovery method proportionate to the evidence. The goal is not merely a quieter PC—it is a system and set of accounts you can trust again.

 

References

  1. orexports.com: GuLoader and AgentTesla Files, Removal - 2-Spyware 2-Spyware 2026-11-16T06:45:33.432000+00:00
  2. Virus and Threat Protection in the Windows Security App | Microsoft Support support.microsoft.com
  3. Microsoft Defender Offline scan in Windows - Microsoft Defender for Endpoint | Microsoft Learn learn.microsoft.com