Cybercriminals used fake Adobe Acrobat document-signing pages to trick Windows users into downloading legitimate ConnectWise ScreenConnect remote-access installers. The installers were digitally signed but preconfigured to connect to unauthorized remote-access tenants, potentially giving an outside operator persistent control of the device. No victim compromises were confirmed, but the campaign provides a realistic document-signing lure that organizations can train against.
How the attack worked
The campaign relied on fake Adobe Acrobat Reader-themed document-signing pages that told visitors they needed to install remote-control software before a document could be signed or viewed. Visitors who followed the call to action downloaded genuine, digitally signed ConnectWise ScreenConnect installers. These installers were not modified malware, but they were preconfigured to connect to two unauthorized ScreenConnect Cloud tenants, identified as omydze and vvvzou. The analyzed clients included a service that starts automatically as LocalSystem, creating a high-confidence risk of persistent remote access for an external operator if the software was installed and run.
Before delivering the client, the fake pages also collected visitor information, including IP address, device and browser details, location, timestamps, and ISP data, through Telegram bots. No victim compromises or credential capture were confirmed in connection with this activity.
Why it succeeded
This lure worked because it exploited a routine business process, document signing, that employees in finance, legal, human resources, and procurement roles encounter regularly. Framing the installation step as a required part of that workflow lowered suspicion. The use of a genuine, digitally signed installer compounded the problem: conventional defenses that check file signatures or block a single installer hash are insufficient here, since legitimate remote-access clients can be built for different unauthorized tenants without changing the underlying signed software.
What to watch for
- A document-signing request that unexpectedly requires installing remote-control or support software.
- A signing page hosted on an unfamiliar domain instead of an approved Adobe or company document-signing service.
- Any remote-access software prompt that was not initiated through an approved IT process.
How to build resistance
Organizations and employees can reduce this risk with a few concrete steps:
- Independently verify any document-signing request that asks for software installation, especially remote-control tools, before downloading anything.
- Treat a valid digital signature as necessary but not sufficient evidence of safety; it does not confirm the software is configured for an approved tenant.
- Encourage employees to report unexpected remote-access prompts to IT or security rather than installing software to complete a document request.
- Security and endpoint management teams should inventory existing remote-management tools, check which accounts control current installations, and investigate any tenant or connection the organization has not approved.
These steps map to recognized techniques including T1566.002, T1204.002, T1219, and T1543.003, and they reinforce that user verification combined with tenant-level monitoring is more effective than signature checks alone.
Key findings
- Fake Adobe Acrobat Reader-themed document-signing pages delivered genuine, digitally signed ConnectWise ScreenConnect installers.
- The ScreenConnect clients were configured to connect to unauthorized ScreenConnect Cloud tenants, identified as omydze and vvvzou.
- The fake pages collected visitor IP address, device and browser information, location, timestamps, and ISP details through Telegram bots before delivering clients.
- The analyzed installers included a service that starts automatically as LocalSystem, creating a high-confidence risk of persistent remote access.
- CloudSEK did not confirm victim compromises or credential capture; the risk described is potential persistent access after a user installs the client.
- Checking a file signature or blocking a single installer hash is insufficient because legitimate remote-access clients can be built for different unauthorized tenants.
Who’s being targeted
- Commonly targeted roles: All employees, Finance, Legal, Human Resources, Procurement, IT support, Endpoint management teams, Security operations teams.
- Affected industries: Cross-industry Windows users, Organizations using document-signing workflows, Organizations using remote-management software.
- Attack channels: website.
- Impersonated: Adobe Acrobat Reader.
Red flags to watch for
- A document-signing request unexpectedly requires installation of remote-control software.
- The site uses an unfamiliar domain rather than an approved Adobe or company document-signing service.
- A digitally signed installer is configured to connect to an unapproved remote-access tenant.
Frequently asked questions
What is the fake Adobe document-signing attack?
Attackers used Adobe Acrobat Reader-themed pages to present a document-signing request that required installing a remote-access client before the document could be viewed or signed.
Was the ScreenConnect installer malware?
No, the installers were genuine, digitally signed ConnectWise ScreenConnect clients. The risk came from their configuration to connect to unauthorized ScreenConnect Cloud tenants rather than from trojanized code.
Why can't a digital signature alone catch this threat?
Because the software is legitimate and signed, file signature or hash checks alone will not reveal that it is configured to connect to an unapproved remote-access tenant.
What should employees do if a signing page asks to install software?
They should independently verify the request before installing anything and report unexpected remote-control software prompts to IT or security rather than proceeding.
Read the video transcript
An Adobe document to sign? Why does it need remote access? A fake page at clickksy dot icu says, 'Install the required client to continue.' The download is a real, digitally signed ConnectWise ScreenConnect installer. Here’s the catch: signed doesn’t mean approved. That installer points to unauthorized tenants, omydze or vvvzou, and could start automatically with powerful system access. If signing a document requires a remote-access install, stop and report the prompt to IT.