Jeld-wen was listed on 18 November 2026 by the Whitearmor ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Whitearmor listed 6 organizations that month and 25 in total.
- Listed 0 days ago.
- 865 organizations were listed by all groups in November 2026, see the month.
- 126 in Manufacturing that month.
- 372 in US that month.
Updated 2026-11-18 13:32 UTC. Data: public leak-site listings. How we work.
Jeld-wen
Threat Group Post & Evidence
- Listed by
- Whitearmor 25 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.
JELD-WEN is a global manufacturer of interior and exterior doors, windows, and related building products for new construction and remodeling, headquartered in Charlotte, NC, and listed on the NYSE under JELD. We hold JELD-WEN's complete customer warranty database: 5.27 million claim records containing the names, emails, phone numbers, and home addresses of 2.3 million customers, plus payment cards with CVV codes, plaintext passwords, and 30,006 employee records including full executive leadership details. Our demand is $700,000 in BTC. Emails were sent to you before this post. We had intended to keep this confidential, but you have yet to respond. You have five days to make contact. If contact is not made, we will leak everything. Emails were sent to the following: [email protected] [email protected] [email protected] [email protected] [email protected] bbrunworth@jel…
Show the full post (1276 characters)
JELD-WEN is a global manufacturer of interior and exterior doors, windows, and related building products for new construction and remodeling, headquartered in Charlotte, NC, and listed on the NYSE under JELD. We hold JELD-WEN's complete customer warranty database: 5.27 million claim records containing the names, emails, phone numbers, and home addresses of 2.3 million customers, plus payment cards with CVV codes, plaintext passwords, and 30,006 employee records including full executive leadership details. Our demand is $700,000 in BTC. Emails were sent to you before this post. We had intended to keep this confidential, but you have yet to respond. You have five days to make contact. If contact is not made, we will leak everything. Emails were sent to the following: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] CONTACT US Email: [email protected] Session: 0547b7f96d469ecb332e89d0108e71c92df5bacff6c4ed5b9801ab5fffe872ee67
Amounts as written
- 30,006 employee
Kinds of data mentioned
-
Passwords and credentials
“…of 2.3 million customers, plus payment cards with CVV codes, plaintext passwords, and 30,006 employee records including full executive leadership details. Our demand is $700,000…”
-
Email and communications
“…customer warranty database: 5.27 million claim records containing the names, emails, phone numbers, and home addresses of 2.3 million customers, plus payment cards with CVV codes,…”
-
Customer or client data
“We hold JELD-WEN's complete customer warranty database: 5.27 million claim records containing the names, emails, phone numbers,…”
-
Employee and HR records
“…customers, plus payment cards with CVV codes, plaintext passwords, and 30,006 employee records including full executive leadership details. Our demand is $700,000 in BTC. Emails…”
-
Databases and backups
“We hold JELD-WEN's complete customer warranty database: 5.27 million claim records containing the names, emails, phone numbers, and home addresses…”
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 Jeld-wen (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 Jeld-wen 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 Jeld-wen 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, email and communications, passwords and credentials, employee and hr 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 Jeld-wen 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 Jeld-wen
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, email and communications, 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.
- 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.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- 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: 30,006 employee. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: Whitearmor listed 2 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)
60/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.