INSPECTING ARCHIVED INTELLIGENCE (OUTDATED VERSION).
OVHcloud CLI Compromised
|
2026-10-20 11:31
HIGH
MEDIUM
MALWARE & BOTNETS
CYBERATTACK (GENERAL)
Executive Summary
AI-generated
On October 19, 2026, an attacker using the compromised GitHub account HassenBF replaced binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0, affecting approximately 250 users who downloaded the maliciously modified tool in roughly 94 minutes before the assets were removed. The attack was attributed to the GlassWorm threat actors, a self-propagating malware and botnet that has consistently targeted software supply chains since its emergence in October 2025. The attacker uploaded locally built binaries directly to the releases, replacing `[IOC HIDDEN • LOGIN REQUIRED]` with malicious files, without modifying source code or tags. As of now, no further updates on the incident have been reported by OVHcloud.
Technical Mitigations AI-generated
• Replace `<a href="/auth/login?next=/detail/djr1XaEBDYL3N98kWLw4" class="ioc-censored-pill text-decoration-none" title="Protected IoC: Sign in to view" data-bs-toggle="tooltip"><span class="badge bg-black text-warning border border-warning border-opacity-75 font-monospace ioc-lock-tag align-middle"><i class="bi bi-lock-fill me-1"></i>[IOC HIDDEN • LOGIN REQUIRED]</span></a>` with a signed version to prevent the attacker from replacing it.
• Detect GlassWorm malware by monitoring for suspicious network activity and system calls related to file operations.
Technical Observables 21 IoCs Login Required
Indicators of Compromise (IoCs) Protected
Raw threat telemetry, malicious IP addresses, file hashes, and direct VirusTotal correlation are restricted to authenticated users.
sha1 1
urls 2
sha256 7
domains 1
files 3
ips 2
md5 5
Intelligence Metadata
Actors / Malware / CVEs / Campaigns
GlassWormGlassWorm
Target & Sectors
Global Scope
technologytechnology
Incident Timeline
Oct. 20, 2025
A poisoned extension installed on a MacBook on October 20, 2025, was the actual vector used by an attacker to steal developer secrets.
Click on any entity below to view its context and source!
organisation
MacBook
However, OVHcloud's security team later discovered the developer installed a poisoned extension on a personal MacBook on Oct. 20, 2025.
March 2026
The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments.
Click on any entity below to view its context and source!
infrastructure
Macos
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
infrastructure
Linux
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
infrastructure
Windows
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
organisation
Intel
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
organisation
Docker
Source builds and Docker images remained unaffected.
organisation
The Blue Report 2026
The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments.
at least March 2026
According to the researchers, it had been compromised since at least March 2026, when four of its personal repositories were rewritten, three of them to include a hidden loader.
October 19
The supply chain incident occurred on October 19, and OVHcloud lists versions v0.11.0 through v0.15.0 as compromised.
Click on any entity below to view its context and source!
organisation
Klaba
Klaba said that the compromised release appeared at 14:47 on October 19 and was detected and blocked at 16:21 after a customer reported it.
infrastructure
11.0
The supply chain incident occurred on October 19, and OVHcloud lists versions v0.11.0 through v0.15.0 as compromised.
infrastructure
15.0
The supply chain incident occurred on October 19, and OVHcloud lists versions v0.11.0 through v0.15.0 as compromised.
October 19, 2026
Threat actors used a compromised GitHub account to replace binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0, potentially stealing developer secrets.
Click on any entity below to view its context and source!
infrastructure
11.0
On October 19, 2026, an attacker using the compromised GitHub account HassenBF replaced binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0.
infrastructure
15.0
On October 19, 2026, an attacker using the compromised GitHub account HassenBF replaced binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0.
organisation
CLI
On October 19, 2026, an attacker using the compromised GitHub account HassenBF replaced binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0.
2026/10/20
Threat actors hijacked a developer's GitHub account to replace existing assets in the OVHcloud CLI tool with malicious binaries, specifically targeting versions 0.11.0 through 0.15.0 of the tool.
Click on any entity below to view its context and source!
infrastructure
Linux
How to Tell
The customer who caught the swap pulled the build information out of the new v0.15.0 Linux arm64 binary with go version -m, which reads the file without running it, and posted it in a
GitHub issue
.
The only published hash of a swapped file is the v0.15.0 Linux arm64 archive:
SHA-256
(swapped archive): 3833daffcaaaab27e4e0e0833240ffcb1df8df648f4ec0bc4a75c176e28933cb
SHA-256
(original archive): 5c2beb56e6d83a4b426565a1557791ef759316abcc4effb38dd627c90aeb80e0
A build without the version flag would report its version as undefined, but running a suspect binary to find out is not adv…
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
infrastructure
Windows
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
Users who installed or updated the CLI on macOS, 64-bit Linux, or Windows x86_64 via the official install script, Homebrew, or a direct GitHub download during the roughly 94-minute window are affected.
organisation
CI
In a second post on Monday night,
quoted by Next
, Klaba wrote that the problem stemmed from the immutability option not being activated, so a user with the right permissions could modify existing releases directly on GitHub without any checks by the company's CI/CD pipeline.
In a later update, Klaba shared that GitHub’s release immutability setting was disabled, allowing a sufficiently privileged account to modify existing releases without passing CI/CD checks.
Additionally, the cloud provider noted that its main
CI/CD
platform for production is run internally on a private Git repository instance, not hosted on GitHub, and thus they were not impacted by the attack.
organisation
GitHub
French cloud computing and web hosting company OVHcloud says a hacker used the GitHub account of one of its developers to plant a secret-stealing binary in its official command-line interface (CLI) tool.
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
OVHcloud CLI releases backdoored on GitHub to steal developer secrets.
organisation
CLI
French cloud computing and web hosting company OVHcloud says a hacker used the GitHub account of one of its developers to plant a secret-stealing binary in its official command-line interface (CLI) tool.
Ran the CLI's own
upgrade command
from a v0.12.0, v0.13.0, or v0.14.0 install on a macOS or Linux machine where the tool was installed by the script or by hand.
French cloud and hosting provider OVHcloud is warning users that attackers compromised its open-source command-line interface (CLI) tool to distribute information-stealing malware.
infrastructure
Macos
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
Ran the CLI's own
upgrade command
from a v0.12.0, v0.13.0, or v0.14.0 install on a macOS or Linux machine where the tool was installed by the script or by hand.
infrastructure
15.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
How to Tell
The customer who caught the swap pulled the build information out of the new v0.15.0 Linux arm64 binary with go version -m, which reads the file without running it, and posted it in a
GitHub issue
.
The only published hash of a swapped file is the v0.15.0 Linux arm64 archive:
SHA-256
(swapped archive): 3833daffcaaaab27e4e0e0833240ffcb1df8df648f4ec0bc4a75c176e28933cb
SHA-256
(original archive): 5c2beb56e6d83a4b426565a1557791ef759316abcc4effb38dd627c90aeb80e0
A build without the version flag would report its version as undefined, but running a suspect binary to find out is not adv…
organisation
Klaba
"The hacker used the GitHub account of one of the developers and added a binary whose job is to retrieve secrets from the disk," Klaba wrote in
an X post
.
In a second post on Monday night,
quoted by Next
, Klaba wrote that the problem stemmed from the immutability option not being activated, so a user with the right permissions could modify existing releases directly on GitHub without any checks by the company's CI/CD pipeline.
Klaba said the compromised version appeared at 14:47 Paris time and was blocked at 16:21, after a customer reported the issue.
infrastructure
16.0
OVHcloud deleted the swapped archives and published a clean
v0.16.0
that evening as an immutable release, whose files GitHub will not let anyone change.
OVHcloud's clean v0.16.0 build reads v0.16.0+dirty.
Check a downloaded archive against the release with gh release verify-asset v0.16.0 FILE, as
GitHub documents
.
organisation
OVHcloud
Octave Klaba, chairman and CEO of OVHcloud, revealed the incident in posts on social media platform X, urging users that downloaded the latest version of tool to "update it again very quickly" or delete it.
French cloud computing and web hosting company OVHcloud says a hacker used the GitHub account of one of its developers to plant a secret-stealing binary in its official command-line interface (CLI) tool.
infrastructure
0.10.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Version 0.10.0 and the newly released version 0.16.0 are clean.
infrastructure
0.16.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Version 0.10.0 and the newly released version 0.16.0 are clean.
organisation
OVHcloud CLI
OVHcloud CLI releases backdoored on GitHub to steal developer secrets.
Hijacked Developer Account Used to Plant Stealer in OVHcloud CLI.
organisation
ForceMemo
The wallet that loader reads is the one named in GlassWorm's
ForceMemo campaign
, which force-pushed malware into hundreds of Python repositories in March with stolen GitHub tokens.
"The wallet is a known GlassWorm indicator, and the amend-and-force-push technique matches the
ForceMemo campaign
.
infrastructure
0.11.0
The attacker hijacked a developer’s GitHub account to gain access to the OVHcloud CLI repository and modify versions 0.11.0 through 0.15.0 of the tool.
infrastructure
0.15.0
The attacker hijacked a developer’s GitHub account to gain access to the OVHcloud CLI repository and modify versions 0.11.0 through 0.15.0 of the tool.
organisation
the OVHcloud CLI
The attacker hijacked a developer’s GitHub account to gain access to the OVHcloud CLI repository and modify versions 0.11.0 through 0.15.0 of the tool.
infrastructure
11.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
infrastructure
12.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
infrastructure
13.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
infrastructure
14.0
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
organisation
Solana
The loader’s next stage queries the Solana blockchain for the location of a further payload, using a wallet that is a known
GlassWorm
indicator.
organisation
UTC
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
organisation
the macOS x86_64
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
organisation
the Linux x86_64
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
organisation
Windows i386
The Linux i386, Windows i386, Windows arm64, and WebAssembly builds were left alone on every release.
organisation
WebAssembly
The Linux i386, Windows i386, Windows arm64, and WebAssembly builds were left alone on every release.
organisation
Hacker News
The Hacker News ran the same command on the clean v0.16.0 Linux x86_64 binary: it reports v0.16.0+dirty, vcs.modified=true and the commit it was built from.
organisation
Linux x86_64
The Hacker News ran the same command on the clean v0.16.0 Linux x86_64 binary: it reports v0.16.0+dirty, vcs.modified=true and the commit it was built from.
organisation
Unicode
The GlassWorm Question
OpenSourceMalware ties the account to
GlassWorm
, the malware campaign that hides code in invisible Unicode characters and fetches its next stage from the memo field of a Solana wallet's transactions.
Tactical Metrics
Metrics
infrastructure
0.11.0
Software Version
Click for context!
The attacker hijacked a developer’s GitHub account to gain access to the OVHcloud CLI repository and modify versions 0.11.0 through 0.15.0 of the tool.
Metrics
infrastructure
0.15.0
Software Version
The attacker hijacked a developer’s GitHub account to gain access to the OVHcloud CLI repository and modify versions 0.11.0 through 0.15.0 of the tool.
Metrics
infrastructure
11.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
On October 19, 2026, an attacker using the compromised GitHub account HassenBF replaced binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0.
The supply chain incident occurred on October 19, and OVHcloud lists versions v0.11.0 through v0.15.0 as compromised.
Metrics
infrastructure
12.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Metrics
infrastructure
13.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Metrics
infrastructure
14.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Metrics
infrastructure
15.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
How to Tell
The customer who caught the swap pulled the build information out of the new v0.15.0 Linux arm64 binary with go version -m, which reads the file without running it, and posted it in a
GitHub issue
.
The only published hash of a swapped file is the v0.15.0 Linux arm64 archive:
SHA-256
(swapped archive): 3833daffcaaaab27e4e0e0833240ffcb1df8df648f4ec0bc4a75c176e28933cb
SHA-256
(original archive): 5c2beb56e6d83a4b426565a1557791ef759316abcc4effb38dd627c90aeb80e0
A build without the version flag would report its version as undefined, but running a suspect binary to find out is not adv…
On October 19, 2026, an attacker using the compromised GitHub account HassenBF replaced binaries on existing OVHcloud CLI releases v0.11.0 through v0.15.0.
The supply chain incident occurred on October 19, and OVHcloud lists versions v0.11.0 through v0.15.0 as compromised.
Metrics
infrastructure
0.10.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Version 0.10.0 and the newly released version 0.16.0 are clean.
Metrics
infrastructure
0.16.0
Software Version
"The compromised versions are v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0," the
CEO said
, adding that older version 0.10.0 and the latest release 0.16.0 were clean.
Version 0.10.0 and the newly released version 0.16.0 are clean.
Metrics
infrastructure
Macos
Affected Product
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
Ran the CLI's own
upgrade command
from a v0.12.0, v0.13.0, or v0.14.0 install on a macOS or Linux machine where the tool was installed by the script or by hand.
Users who installed or updated the CLI on macOS, 64-bit Linux, or Windows x86_64 via the official install script, Homebrew, or a direct GitHub download during the roughly 94-minute window are affected.
Metrics
infrastructure
Linux
Affected Product
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
The Linux i386, Windows i386, Windows arm64, and WebAssembly builds were left alone on every release.
Ran the CLI's own
upgrade command
from a v0.12.0, v0.13.0, or v0.14.0 install on a macOS or Linux machine where the tool was installed by the script or by hand.
How to Tell
The customer who caught the swap pulled the build information out of the new v0.15.0 Linux arm64 binary with go version -m, which reads the file without running it, and posted it in a
GitHub issue
.
The Hacker News ran the same command on the clean v0.16.0 Linux x86_64 binary: it reports v0.16.0+dirty, vcs.modified=true and the commit it was built from.
The only published hash of a swapped file is the v0.15.0 Linux arm64 archive:
SHA-256
(swapped archive): 3833daffcaaaab27e4e0e0833240ffcb1df8df648f4ec0bc4a75c176e28933cb
SHA-256
(original archive): 5c2beb56e6d83a4b426565a1557791ef759316abcc4effb38dd627c90aeb80e0
A build without the version flag would report its version as undefined, but running a suspect binary to find out is not adv…
A customer's CI job caught the swap because it pins the SHA-256 of the Linux arm64 archive and began failing.
Users who installed or updated the CLI on macOS, 64-bit Linux, or Windows x86_64 via the official install script, Homebrew, or a direct GitHub download during the roughly 94-minute window are affected.
Metrics
infrastructure
Windows
Affected Product
According to OpenSourceMalware's report, affected platforms are macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64.
They were live on GitHub for up to 94 minutes, from 12:47 to 14:21 UTC, and reached only people who installed or updated the OVHcloud CLI during that window, via a path that checks for no hash, on macOS, Linux x86_64 or arm64, or Windows x86_64.
Who Was Exposed
On v0.15.0, the attacker replaced six files: the macOS x86_64 and arm64 archives, the Linux x86_64 and arm64 archives, the Windows x86_64 archive, and the checksums.txt file, so the published hashes matched the new binaries.
The Linux i386, Windows i386, Windows arm64, and WebAssembly builds were left alone on every release.
Related:
Decades-Old Windows Utility Powers Modern ClickFix Attack
Users who installed or updated the CLI on macOS, 64-bit Linux, or Windows x86_64 via the official install script, Homebrew, or a direct GitHub download during the roughly 94-minute window are affected.
Metrics
infrastructure
16.0
Software Version
OVHcloud deleted the swapped archives and published a clean
v0.16.0
that evening as an immutable release, whose files GitHub will not let anyone change.
OVHcloud's clean v0.16.0 build reads v0.16.0+dirty.
Check a downloaded archive against the release with gh release verify-asset v0.16.0 FILE, as
GitHub documents
.
The release workflow never ran: the run list shows no workflow between October 16 and the v0.16.0 tag push at 16:00 UTC on Monday.
Metrics
infrastructure
15.1-0
Software Version
Three things mark the bad build:
The module line reads v0.15.1-0.20261013083505-5ead8ef9b43d+dirty, a pseudo-version, the stand-in string Go generates for a build from an untagged commit, here one from October 13.
Metrics
infrastructure
250
Downloads
The activity lasted approximately 94 minutes, and roughly 250 downloads occurred before the assets were removed.
Intelligence Sources
AlienVault OTX
2026-10-25
Dark Reading
2026-10-21
The Hacker News
2026-10-20
BleepingComputer
2026-10-20
SecurityWeek
2026-10-21
Unpublish from Social Media?
Are you sure you want to delete this podcast video from all synchronized social networks (YouTube, Facebook, Threads)?
Important:
Due to Meta API restrictions, Instagram Reels cannot be deleted automatically via API by third-party apps.
View Profile to Delete Manually
View Profile to Delete Manually
Tactical Intelligence
Report Intelligence Issue
Podcast Options
Generate
Incident Version History
CURRENT VERSION
Last Updated: 2026-11-12T11:19
Comprehensive Tactical Telemetry
Highly Correlated Entities
31x
organisation
Identified Entity
the OVHcloud CLI
entity
16x
timeline
Temporal Reference
2026/10/19
date
11x
infrastructure
Software Version
0.11.0
version
4x
tactic
MITRE ATT&CK Technique
T1588.001 - Malware
technique
3x
infrastructure
Affected Product
Macos
software
3x
general metric
Minutes
94
minutes
2x
tactic
Cyber Operation Type
Botnet
tactic
Contextual Telemetry
Context Block
5 METRICS
target region
Target Country
France
country
malware
Malware Payload
GlassWorm
tool
general metric
V0.15.1
0
v0.15.1
general metric
Downloads / Installs
250
downloads
infrastructure
Downloads
250
downloads
Click on any entity below to view its context in the main text!
Selective Unpublish
Select the networks you want to remove this post from. The system will try to delete the real post through the API and clean the database so you can publish it again.
By navigating this website, you accept the use of strictly necessary technical cookies for session security and basic platform functionality. We do not use tracking or advertising cookies. Read our Privacy Policy.
Generating report…
0s