Suspicious Certificate Issuer Detected in MAX Messenger Windows Update Package

A detailed observation from a security researcher highlights an unexpected change in the code signing certificate for the MAX messenger desktop client on Windows. The August update package was signed by an individual named Konstantin Syomochkin instead of the usual Communication Platform LLC. This discrepancy raised concerns about potential supply chain interference linked to recent EU sanctions against the developer. The certificate was issued shortly after sanctions and belongs to a person based in Astana, Kazakhstan, with limited public ties to the VK team. Official MSI installers downloaded directly from the MAX website remain signed by the company, while the client-triggered update differs in both version and signer. The researcher recommends that VK verify the download chain through Mail.ru trackers to rule out tampering. Installation of the update was declined pending further clarification.

HabrTranslated from Russian

Read at source

A security researcher has reported an unusual change in the code signing certificate used for the MAX messenger desktop client on Windows during its August update cycle.

The original installer MAX.msi and previous updates were consistently signed by Communication Platform LLC, matching the publisher information shown by Windows User Account Control. In the August update, triggered via the client's built-in check, the signer suddenly appeared as an unknown individual named Konstantin Syomochkin.

Background and Observations

The researcher noted that the certificate for Konstantin Syomochkin was issued only two weeks after the latest EU sanctions package. The individual is listed as residing in Astana, Kazakhstan, with prior mentions as an Android developer on Stack Overflow and at the Mobius 2023 Spring conference, but no clear affiliation with the VK team in employee lists.

Direct downloads of version 26.23.0 from the official MAX site for both standard and Yandex-branded MSI files showed the expected company signature. In contrast, the client-initiated update package (version 26.27.3) carried the private certificate and was smaller in size.

Potential Supply Chain Implications

The researcher suggests the anomaly could stem from an emergency workaround after sanctions forced certificate revocation by authorities such as GlobalSign, similar to actions taken in June. All download requests appear to route through Mail.ru trackers to endpoints under download.cdn.oneme.ru.

Because the mismatch could indicate either an internal signing change or external interference in the update delivery chain, the update was not installed. The case has been shared publicly to prompt verification by the VK team responsible for the messenger.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Supply Chain & Open Source

Passwordless Kubernetes Image Pulling with Artifact Keeper via ServiceAccount Tokens
Malicious Code Injected into LiteLLM Open Source AI Package via Supply Chain Attack
GhostAction Campaign Compromises 790 GitHub Repositories via Malicious Workflows