Allmand-Smith Limited was listed on 21 October 2026 by the aurora ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). aurora listed 17 organizations that month and 61 in total.
- Listed 30 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 191 in Manufacturing that month.
- 36 in GB that month.
Updated 2026-11-19 05:32 UTC. Data: public leak-site listings. How we work.
Allmand-Smith Limited
Threat Group Post & Evidence
- Listed by
- Aurora 61 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.
[distributor, manufacturer] Allmand-Smith Limited (trading as Stormguard) — a UK manufacturer and distributor of building products headquartered in Stoke-on-Trent. Domain admin credentials in plaintext and a full DC dump — STORMGUARD\MichaelAdmin / 5t0rmGuard Complete NatWest banking infrastructure — blfw.db (21.3 MB live Bankline database with account numbers, sort codes, payee details, and transaction logs), plus WorldPay payment gateway credentials (WorldPay Account Details.xlsx), plus Sage 200 AR/AP containing bank details for every customer and supplier across all 15 entities. NatWest has 3 outstanding registered charges (Jun 2026). Full payroll for every employee, current and former — Payroll.zip (6.1 GB, 1,185 files) from Sage Payroll: NI numbers (lifetime identifiers), tax codes, PAYE history, gross/net pay per period, bank account details for BACS salary payments, pension contri…
Show the full post (1443 characters)
[distributor, manufacturer] Allmand-Smith Limited (trading as Stormguard) — a UK manufacturer and distributor of building products headquartered in Stoke-on-Trent. Domain admin credentials in plaintext and a full DC dump — STORMGUARD\MichaelAdmin / 5t0rmGuard Complete NatWest banking infrastructure — blfw.db (21.3 MB live Bankline database with account numbers, sort codes, payee details, and transaction logs), plus WorldPay payment gateway credentials (WorldPay Account Details.xlsx), plus Sage 200 AR/AP containing bank details for every customer and supplier across all 15 entities. NatWest has 3 outstanding registered charges (Jun 2026). Full payroll for every employee, current and former — Payroll.zip (6.1 GB, 1,185 files) from Sage Payroll: NI numbers (lifetime identifiers), tax codes, PAYE history, gross/net pay per period, bank account details for BACS salary payments, pension contributions, P45/P60 records. Complete financial records for 15 entities — Sage 200 databases for Allmand-Smith Ltd, Stormguard Fabrications, Stormguard Sills, Rainwater Systems, Floodplan, Bridgemill, Chelford, Paradise, MJ Associates, SAS Partners, Specialised Aluminium Supplies, two pension funds, plus the consolidated age200_AllmandSmithLtd.bak (2.1 GB). Management accounts (Jan–Jul 2024), nominal trial balances, bank reconciliations (£102,662 cash at year-end). Revenue: £17.66M, profit: £1.01M, financial health: 12/100 (distressed).
Amounts as written
- 21.3 MB
- 6.1 GB
- 1,185 files
- 2.1 GB
Kinds of data mentioned
-
Tax records
“…GB, 1,185 files) from Sage Payroll: NI numbers (lifetime identifiers), tax codes, PAYE history, gross/net pay per period, bank account details for BACS salary payments,…”
-
Banking and wire details
“…(lifetime identifiers), tax codes, PAYE history, gross/net pay per period, bank account details for BACS salary payments, pension contributions, P45/P60 records. Complete financial…”
-
Payroll and salaries
“…entities. NatWest has 3 outstanding registered charges (Jun 2026). Full payroll for every employee, current and former — Payroll.zip (6.1 GB, 1,185 files) from Sage Payroll:…”
-
Passwords and credentials
“Domain admin credentials in plaintext and a full DC dump — STORMGUARD\MichaelAdmin / 5t0rmGuard Complete NatWest banking…”
-
Customer or client data
“…Account Details.xlsx), plus Sage 200 AR/AP containing bank details for every customer and supplier across all 15 entities. NatWest has 3 outstanding registered charges (Jun 2026).…”
-
Employee and HR records
“…has 3 outstanding registered charges (Jun 2026). Full payroll for every employee, current and former — Payroll.zip (6.1 GB, 1,185 files) from Sage Payroll: NI numbers (lifetime…”
-
Databases and backups
“Domain admin credentials in plaintext and a full DC dump — STORMGUARD\MichaelAdmin / 5t0rmGuard Complete NatWest banking infrastructure — blfw.db (21.3…”
Plain-English summary AI-written
The group says it holds domain credentials, a domain controller dump, banking and payment information, customer and supplier bank details, and payroll records for current and former employees of Allmand-Smith Limited, trading as Stormguard.
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 Allmand-Smith 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 Allmand-Smith 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 Allmand-Smith 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, passwords and credentials, employee and hr records.
- Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: banking and wire details, payroll and salaries, tax records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
Within 30 days
- Keep watching Allmand-Smith 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 Allmand-Smith 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: passwords and credentials, customer or client data, payroll and salaries.
- Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: banking and wire details, payroll and salaries.
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.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- 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: 21.3 MB, 6.1 GB, 1,185 files. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties United Kingdom: UK GDPR requires notifying the ICO within 72 hours of becoming aware of a reportable personal data breach. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United Kingdom.
Within 30 days
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: aurora listed 9 other Manufacturing organization(s) in the last 90 days.
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)
69/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 IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Launch Attack Surface Recon →Run a free passive scan on your own domain to see what an attacker can see from the outside.