Globacom Limited was listed on 26 July 2023 by the alphv ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). alphv listed 417 organizations that month and 717 in total.
- Listed 1212 days ago.
- 904 organizations were listed by all groups in July 2023, see the month.
- 87 in Technology that month.
- 1 in NG that month.
Updated 2026-11-19 06:48 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- ALPHV / BlackCat 717 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
Globacom Limited, commonly known as Glo, is a Nigerian multinational telecommunications company with annual revenue about $1.3B. Network of this company has been breached and over 600Gb of data were leaked from there. Now we are offering top management of Gloworld and Mike Adenuga specially to contact us in next 3 days to protect this stolen data. In case if they will completely refuse to negotiate all data related to Gloworld will be exposed for free download. These data contains following information: - payments - financial data of your company - financial data of your employees - signed contracts and agreements - employees personal data - phone call records - simcards registrations with abonent data - phone calls detailed tracing of your all registered numbers - full clients base with all data related Management of Globacom Limited decided to hide this incident and not to inform both …
Show the full post (1067 characters)
Globacom Limited, commonly known as Glo, is a Nigerian multinational telecommunications company with annual revenue about $1.3B. Network of this company has been breached and over 600Gb of data were leaked from there. Now we are offering top management of Gloworld and Mike Adenuga specially to contact us in next 3 days to protect this stolen data. In case if they will completely refuse to negotiate all data related to Gloworld will be exposed for free download. These data contains following information: - payments - financial data of your company - financial data of your employees - signed contracts and agreements - employees personal data - phone call records - simcards registrations with abonent data - phone calls detailed tracing of your all registered numbers - full clients base with all data related Management of Globacom Limited decided to hide this incident and not to inform both regulators and customers. Globacom's top management has last chance July 29rd, if they want to protect data of Globacom's business, partners and customers.
Amounts as written
- 600Gb
Kinds of data mentioned
-
Customer or client data
“…data - phone calls detailed tracing of your all registered numbers - full clients base with all data related Management of Globacom Limited decided to hide this incident and…”
-
Employee and HR records
“…information: - payments - financial data of your company - financial data of your employees - signed contracts and agreements - employees personal data - phone call records - simcards…”
-
Contracts and legal files
“…financial data of your company - financial data of your employees - signed contracts and agreements - employees personal data - phone call records - simcards registrations with…”
Plain-English summary AI-written
The group says it holds over 600 GB of stolen data, including company and employee financial information, contracts, employees’ personal data, phone call records, and SIM card registrations.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Globacom Limited (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Globacom Limited directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Globacom Limited can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, employee and hr records.
Within 30 days
- Keep watching Globacom Limited A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Globacom Limited
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 600Gb. Treat group figures as unverified.
- Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
- Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
-
Check the ways alphv is reported to get in
Check these first; they are how the group is reported to work in general.
- Affiliates impersonate IT or help-desk staff by phone or SMS to obtain credentials, and use the Evilginx2 framework to capture MFA codes and session cookies. (update of Feb 2024)
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
79/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.