SOCLYDE logo
Current languageEN
Cybersecurity newsMalwareWorkstationsSecrets

Valleyrat: signed adware used to deploy a backdoor

The ValleyRAT campaign shows how a signed installer presented as adware can load a backdoor and target secrets on a workstation.

IT team reviewing software installation on a workplace device

In summary

  • A digital signature does not prove that a distributed or modified installer is safe.
  • ValleyRAT can collect keystrokes, clipboard data, screenshots, and additional modules.
  • Antivirus exclusions and unapproved installations greatly increase the impact of a compromised workstation.
Article contents

The software people seek can hide another function

On August 31, 2026, Kaspersky described a campaign in which the ValleyRAT backdoor was distributed with a wallpaper management tool presented as adware. The installer deployed a malicious library through DLL sideloading, added startup persistence, and attempted to disable Windows Defender.

The campaign mainly affected China and India, with more than 1,500 users identified by Kaspersky. Its wider lesson is not geographic: software that a user deliberately installs can receive far more trust than it deserves.

Why a signature is not enough

A signed file may come from a real publisher while being distributed in the wrong context, bundled with another component, or used to load an unsigned malicious DLL. Users also sometimes add a program to an antivirus exclusion to make it work, removing an important barrier.

ValleyRAT can record keystrokes, read the clipboard, capture the screen, and load other modules. On a business workstation, those functions can expose passwords shown temporarily, recovery codes, customer data, and active browser sessions.

A small team's practical response

  • Allow software installation through a known list and process.
  • Do not add downloaded software to an antivirus exclusion just to make it run.
  • Remove local administrator rights when the work does not require them.
  • If suspicious software was installed, isolate the workstation before changing passwords from that same device.
  • Revoke sessions and rotate secrets accessible from it: email, cloud, VPN, browser, and vault.
  • Rebuild from a trusted image when persistence or access scope cannot be ruled out.

What Soclyde can and cannot do

A local-first vault does not make an infected workstation trustworthy. Soclyde can still help keep secrets unique and speed up rotation after a device is isolated. A replaced password should not be copied into a temporary file or shared in a conversation.

Soclyde's infostealer guide explains the boundary between the vault, browser, endpoint, and sessions. Each layer needs its own control.

The takeaway

Security starts before installation. A popular, signed, or search-recommended application is still code to execute. A workstation without unnecessary privileges, an unbypassed endpoint defense, and unique secrets reduce a backdoor's reach.


Frequently asked questions

Is signed software always legitimate?

No. A signature helps identify a publisher, but it does not prove that the distributed file is the expected one or that a signed process cannot load a malicious library.

What should happen after a suspicious install?

Isolate the workstation, preserve useful evidence, revoke sessions and secrets accessible from it, then rebuild from a trusted base with help from your provider or security team.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading