On 18 November 2026, the WhiteArmor extortion group added Jeld-Wen to its Tor leak site. Jeld-Wen is a door and window manufacturer based in Charlotte, North Carolina, and its shares trade on the New York Stock Exchange under the ticker JELD. WhiteArmor says it holds the company's full customer warranty database, which it describes as 5.27 million claim records covering 2.3 million customers. It also claims 30,006 employee records and is demanding $700,000 in Bitcoin, with a five-day deadline. Jeld-Wen has not commented publicly. Its most recent SEC filing is the quarterly report for the period ended 26 September 2026, which was filed before the claim and does not address it. Nobody has independently checked the data. The claim still deserves attention, because two earlier WhiteArmor victims, Maersk and J.B. Hunt, have since confirmed breaches.
What Happened
WhiteArmor's leak-site post, reproduced in full by HookPhish, says the group emailed about 18 Jeld-Wen addresses before going public. The post says: "We had intended to keep this confidential, but you have yet to respond." It gives five days to make contact and threatens to "leak everything" if Jeld-Wen does not. That puts the deadline at about 23 November 2026. HookPhish logged the listing at 13:08 UTC on 18 November.
Several trackers picked up the listing on the same day:
- ThreatMon flagged Jeld-Wen as a new WhiteArmor victim. Undercode News notes that ThreatMon's alert included no technical evidence, no data sample and no ransom details.
- Dark Web Intelligence (@DailyDarkWeb) shared the full list of claimed data, as reported by Undercode News.
- QPulse cites Ransomware.live, which calls WhiteArmor an emerging group and says the claim should be treated with caution until it can be verified.
As of publication, Jeld-Wen has not issued a statement. No regulator filing or breach notification has appeared, and no outlet has reported checking a sample of the data. Jeld-Wen is an accelerated filer with the SEC, so if it decides the incident is material, it would have to disclose it on Form 8-K under Item 1.05.
What Was Taken
Everything below comes from WhiteArmor's own post. None of it has been verified.
- Warranty claim records: 5.27 million, which the group says come from Jeld-Wen's complete customer warranty database.
- Customers: 2.3 million, with names, email addresses, phone numbers and home addresses. One Undercode News headline says "23 Million Customers", but the body of the same article and every other report give 2.3 million. The headline looks like a dropped decimal point.
- Payment cards, including CVV codes. No count has been given.
- Plaintext passwords. The group has not said whose accounts they belong to or how many there are.
- Employee records: 30,006, which the group says include "full executive leadership details".
This list should be read with some suspicion. Payment card rules (PCI DSS) forbid storing CVV codes after a transaction is authorised, and a well-run warranty system should not keep passwords in plaintext. If the data turns out to be real, Jeld-Wen's data handling has serious problems. If it does not, the group has padded its claim with the kinds of data that put the most pressure on a victim to pay.
Why It Matters
WhiteArmor appeared recently but has moved fast. DarkWebSonar counted 17 named victims between 20 October and mid-November 2026, across seven countries. They include Maersk ($5M demand), Unilever ($15M), Hisense ($5M), J.B. Hunt ($5M), Ryder ($20M), Echo Global Logistics ($10M), Whirlpool, Disney and LoveSac. Jeld-Wen's $700,000 demand is far lower than any of these. That could mean the group values the data less, or that it is trying a price it expects a company to pay quickly.
The group's track record is mixed but not empty, and accounts of past incidents do not always agree:
- Maersk: BleepingComputer reports that Maersk confirmed an attacker broke into a local legacy system that came with an acquired company, and took data from it. WhiteArmor claims about 100GB from the former LF Logistics platform. Maersk says early findings show "no sensitive data has been disclosed". RedEye Security notes that Maersk's statement does not name WhiteArmor, and that almost every detail about what was taken comes from the attacker.
- J.B. Hunt: DarkWebSonar reports that the company has filed breach notifications and faces class actions.
Its earlier victims were mostly logistics and consumer-goods companies, so Jeld-Wen extends the list into building-products manufacturing. If the employee data is real, executive details give attackers what they need to impersonate leaders in payment fraud schemes (business email compromise) and to target staff with phishing. If the customer data is real, attackers could send convincing fake warranty emails and SMS messages to homeowners.
The Attack Technique
Nobody has said how anyone got into Jeld-Wen's systems. No security vendor has published analysis of a WhiteArmor encryptor or toolset. According to DarkWebSonar, every WhiteArmor listing so far has been about stolen data, and no incident report has confirmed that ransomware actually encrypted a victim's systems. In practice, WhiteArmor behaves like a data-theft extortion group, even though it calls itself a ransomware group.
DarkWebSonar also captured a recruitment campaign from the group's own channels, called "Project Trojan Horse". In it, WhiteArmor offers to buy access from insiders and from brokers who sell access to breached networks. It is looking for:
- Okta, Azure and other identity and access management accounts
- CRM platforms
- Jenkins build servers
- VPN appliances: Fortinet, Cisco AnyConnect, Citrix and SonicWall
The post sets a minimum target revenue of $500 million, and Jeld-Wen is well above that. It also excludes organisations in CIS countries. That exclusion is common among crews operating from former Soviet states, but no one has linked WhiteArmor to a specific country or group. In the Maersk case, the way in was an acquired legacy system that had never been fully absorbed into Maersk's own IT. Whether Jeld-Wen was breached the same way, through bought credentials, an insider, or something else is unknown.
What Organizations Should Do
- Check identity and remote-access logs on the platforms WhiteArmor says it is buying access to: Okta, Azure, VPN appliances and Jenkins. Look for logins from new locations or devices, unexpected MFA enrolments, and service accounts used outside their normal pattern.
- Prepare for insider-sold access. Review who has privileged access, remove leftover accounts from contractors and staff who have left, and alert on large data exports from CRM and customer-service systems.
- Find and secure acquired or legacy systems that still run outside your main security monitoring. That gap was how Maersk was breached.
- Clean out sensitive data you shouldn't hold. Check warranty, support and customer-portal databases for stored CVV codes, full card numbers and passwords that are not hashed, and get rid of them.
- Warn customers and staff about lures that use this incident, especially fake warranty-claim messages and messages impersonating executives. Jeld-Wen customers and dealers should verify any message about the incident through known Jeld-Wen contacts.
- Watch for the deadline passing on or around 23 November. If WhiteArmor publishes data, check it for your organisation's domains, supplier records and reused credentials, and reset any passwords found in it.
Sources: Whitearmor Ransomware Group Claims Data Exfiltration from Jeld-wen... | JELD-WEN Holding, Inc. Form 10-Q for the period ended September 26,... | Maersk confirms data breach as WhiteArmor ransomware demands ... | Jeld-wen Data Breach: Whitearmor Ransomware Claim (Nov 2026) | WhiteArmor Claims Massive JELD-WEN Customer Data Theft, Allegedly E... | WhiteArmor Claims JELD-WEN as New US Manufacturing Victim in Latest... | Dark Web Most Wanted: WhiteArmor DarkWebSonar | Maersk Confirms Breach of an Inherited Legacy System as ...