Central Bank of Gambia
bd_9671ffb44f1a26ac · schema v1 · pii pii-v1
Full breach record for Central Bank of Gambia →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group ALPHV / BlackCat on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
!!!UPDATE!!! You can download some of the data at the link below (TOR). We are currently negotiating the sale of the rest of the data, if you want to participate in the auction and become a buyer of financial and personal data CBGM can write to this e-mail: [REDACTED-EMAIL] Bidding for the sale of data will end on December 7. DATA LINK: http://ra4uys2f4pslov55oj23ckudpbmovj7brrqqnzwu25ux5ul62crbkryd.onion/CBG/ HTTPS://CBG.GM CBG.GM is the central bank of The Gambia. Its name is abbreviated to CBG. The bank is located in Banjul and was established in 1971. The mandate of the Central Bank of The Gambia in accordance with the CBG Act 2005 is as follows: . Achieve and maintain price stability; . Promote and maintain the stability of the currency of The Gambia; . Direct and regulate the financial, insurance, banking and currency system in the interest of the economic development of The Gambia; and . Encourage and promote sustainable economic development and the efficient utilization of the resources of The Gambia through the effective and efficient operation of a financial system.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 8, 2022
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs