vendor binary

The MonPass Certificate Authority Client Backdoor

Updated 5 Oct 2026 · Incident date 8 Feb 2021

The MonPass client installer from a Mongolian certificate authority loaded a Cobalt Strike beacon from 8 February to 3 March 2021.

Avast found the backdoor on 24 March 2021 and published its report on 1 July 2021. MonPass confirmed on 29 June 2021 that it had fixed the issues and told affected customers.

What happened

Attackers broke into the public web server of MonPass and replaced the client installer with a backdoored build.

  • Avast found eight different webshells and backdoors on the server.
  • The poisoned installer downloaded a bitmap image from an attacker server.
  • The code took every fourth byte of the image data, starting from the third byte, and decrypted the result with the XOR key miat_mg.
  • It ran a Cobalt Strike beacon.
  • It stopped if the processor count, memory or disk size looked like an analysis machine.

The installer was online from 8 February to 3 March 2021. Avast was not able to link the attack to a group with confidence.

Affected versions

  • The sources give no version numbers.
  • The affected file is the MonPass client installer.
  • Anyone who downloaded the client from the MonPass website between 8 February and 3 March 2021 is affected.

Indicators of compromise

  • SHA-256 hashes listed by Avast: e2596f015378234d9308549f08bcdca8eadbf69e488355cddc9c2425f77b7535, f21a9c69bfca6f0633ba1e669e5cf86bd8fc55b2529cd9b064ff9e2e129525e8, 4a43fa8a3305c2a17f6a383fb68f02515f589ba112c6e95f570ce421cc690910, and others in the Avast IoC repository.
  • Files named DNS.exe, Browser_plugin.exe, and Silverlight_ins.exe.
  • Payload URLs on download.google-images.ml:8880, micsoftin.us:2086, 37.61.205.212:8880, and jquery-code.ml.
  • The PDB path C:\Users\test\Desktop\fishmaster\x64\Release\fishmaster.pdb and the string Bidenhappyhappyhappy in the samples.
  • The full list is at github.com/avast/ioc.

How to check

Hash the installer you saved and compare it with the Avast list. On macOS or Linux:

shasum -a 256 MonPass-installer.exe

On Windows, use PowerShell.

Get-FileHash .\MonPass-installer.exe -Algorithm SHA256

What to do now

  1. Find every machine that installed the MonPass client between 8 February and 3 March 2021.
  2. Compare hashes and logs with the Avast indicators.
  3. If a match exists, treat the machine as compromised. A Cobalt Strike beacon gives the operator remote control.
  4. Reinstall the client from the current MonPass site and reset the passwords used on the machine.

Frequently asked questions

Who was behind the MonPass backdoor?

Avast reports circumstantial evidence of a China-based espionage group. It was not able to link the attack to a group with confidence.

What did the installer load?

It took a hidden payload out of a downloaded image and ran a Cobalt Strike beacon.

Sources

  1. decoded.avast.io/luigicamastra/backdoored-client-from-mongolian-ca-monpass/
  2. gendigital.com/blog/insights/research/backdoored-client-from-mongolian-ca-monpass
  3. therecord.media/mongolian-certificate-authority-hacked-eight-times-compromised-with-malware

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library