--- title: "Superyacht Cyber Intelligence Special: Binance and the Fridge Hacks" description: "Special briefing: the record Binance crypto theft that began with a fake job interview, and the European fridge hacks, with lessons for crew crypto and critical onboard systems." --- [Skip to content](https://trustanchorpoint.com/insights/superyacht-cyber-intelligence-special-binance-and-the-fridge-hacks#main-content) [![Anchorpoint logo black](https://trustanchorpoint.com/hs-fs/hubfs/Black-White.png?width=1100&height=300&name=Black-White.png)Homepage](https://trustanchorpoint.com) - [What's a virtual CISO?](https://trustanchorpoint.com/whats-a-virtual-ciso) - Superyacht Cybersecurity - [Hire a virtual Cybersecurity Officer (vCySO)](https://trustanchorpoint.com/cybersecurity-compliance-for-superyachts) - [Cybersecurity Compliance for Superyachts](https://trustanchorpoint.com/cybersecurity-compliance-for-superyachts) - [Cybersecurity Awareness Training for Superyacht Crew](https://trustanchorpoint.com/cybersecurity-awareness-training-for-superyacht-crew) - [Cybersecurity Threat Intelligence for Superyacht Crew](https://trustanchorpoint.com/cybersecurity-threat-intelligence-for-superyacht-crew) - [Insights](https://trustanchorpoint.com/insights) - [About](https://trustanchorpoint.com/about-us) - [Code of Ethics](https://trustanchorpoint.com/code-of-ethics) [Contact us](https://trustanchorpoint.com/contact) - [What's a virtual CISO?](https://trustanchorpoint.com/whats-a-virtual-ciso) - Superyacht Cybersecurity - [Hire a virtual Cybersecurity Officer (vCySO)](https://trustanchorpoint.com/cybersecurity-compliance-for-superyachts) - [Cybersecurity Compliance for Superyachts](https://trustanchorpoint.com/cybersecurity-compliance-for-superyachts) - [Cybersecurity Awareness Training for Superyacht Crew](https://trustanchorpoint.com/cybersecurity-awareness-training-for-superyacht-crew) - [Cybersecurity Threat Intelligence for Superyacht Crew](https://trustanchorpoint.com/cybersecurity-threat-intelligence-for-superyacht-crew) - [Insights](https://trustanchorpoint.com/insights) - [About](https://trustanchorpoint.com/about-us) - [Code of Ethics](https://trustanchorpoint.com/code-of-ethics) [Contact us](https://trustanchorpoint.com/contact) # Superyacht Cyber Intelligence Special: Binance and the Fridge Hacks ![Matt](https://app.hubspot.com/settings/avatar/618f3d942fdcc567e50ece243104b38b) Matt November 5, 2026 CyIntel - Special briefing Two incidents from the last few weeks that every crew member should understand: the largest crypto theft on record, which began with a fake job interview, and attacks that cooked the contents of supermarket fridges across Europe. Deckies have a reputation for putting their wages and tips into crypto, and the fridge attacks are a warning for every control system onboard, not just the galley. Both come down to the same thing, who holds the keys and what they can do with them. Plain English first. Technical detail for whoever looks after your onboard systems sits under each section. Special briefing: 5 November 2026 · Covers: Binance theft (29 Oct) and European refrigeration attacks (11 Oct to 3 Nov) · Snapshot, check vendor pages for later changes TL;DR ## The short version Don't have the exact product named? Check the nearest equivalent. If it has not been updated since August 2025, treat it as out of date. 1**Crypto on an exchange.** If your wages or tips sit in crypto on Binance, turn on an authenticator app or passkey, set a withdrawal allow-list and anti-phishing code, and ignore any message offering "compensation". A different exchange: check the same settings, and how it says it would cover a theft. 2**Job offers and downloads.** The Binance attack started with a fake recruiter and a "coding assignment". Be wary of unsolicited job approaches, never run files or software sent by a stranger on a device you use for work or money, and install apps only from official sources. Never approve a wallet request you do not understand, and keep your recovery phrase out of photos and cloud notes. 3**Admin rights onboard.** The attackers worked through a chain of engineers' computers until they reached a system that could sign for everything. Ask who has admin accounts on the yacht's systems, whether any are shared, and what happens if one laptop or phone is compromised. 4**Fridges are only the example.** The same weakness applies to air conditioning, chillers, power and generator controls, alarm and monitoring systems and anything else with a network port. Ask which onboard control systems are on the network or have remote vendor access, and which of them matter for safety. Danfoss, Copeland or Dixell controllers: check firmware and default passwords. A different make: check when it was last updated. 5**Independent alarms and manual fallbacks.** Fit alarms that do not rely on the controller they are watching, practise running critical plant manually, and agree a plan for moving high-value provisions if temperatures rise. 6**Remote access and updates.** Vendor remote access should be approved per session and logged, and no remote updates should run while the yacht is manoeuvring, in port or on a critical power change. Not sure whether any of this applies to your vessel? Contact us and we will check it with you. Priority 1 of 5 ## The Binance hack: what happened Exploited Critical ### In plain English If you are one of the many deckies who put wages and tips into crypto and trade it between watches, this one is for you. On 29 October, attackers emptied Binance's "hot wallets", the connected wallets an exchange uses to move customers' money day to day. Binance puts the impact at about 6.34 billion US dollars, the largest crypto theft ever recorded. Binance says the FBI has indicated North Korea is responsible, and independent analysts had already pointed to North Korea's TraderTraitor group, which has targeted crypto firms before. North Korea denies it. On 3 November Binance published its own account of how it started, and it is a lesson for everyone. In September, a Binance software engineer was approached through a job platform by someone posing as a recruiter. After video interviews with fake staff, he was told to download a "coding assignment" onto his work computer. Binance says it carried malware its security tools missed. Earlier, in June, another engineer's computer had been compromised through a tampered software installer. From those footholds the attackers moved from computer to computer, helped by an internal tool, until they reached a system that could approve payments. They then used stolen credentials to finish the job on 29 October. Binance says it has replenished 98 percent of the affected assets from company funds, reopened withdrawals in stages, and that users should not be affected. Around 2.85 billion dollars has been frozen. If you keep your tips or salary on an exchange, this is the risk: your money is only as safe as the exchange's own access controls. ### What to do - If you hold crypto on Binance, check your account for unexpected logins or withdrawals and read only Binance's official channels for updates. - Treat any message offering compensation, refunds or "wallet verification" as a scam until proven otherwise. Scammers follow every big hack. - Use an authenticator app or passkey rather than text-message codes, and set a withdrawal allow-list if the exchange offers one. - A different exchange: the same lesson applies. Check its security settings and what it says about covering a theft. - Contact IT support if unsure. This is general security information, not financial advice. \+Technical detail for your onboard technical person Tap to open / close ▾ | Reference | Issue | Date | Fix and status | | --- | --- | --- | --- | | Binance hot wallet theft | About 6.34 billion US dollars of assets impacted (Binance), across roughly ten to eleven blockchains depending on the count, including Ethereum, Bitcoin (18,270 BTC), Tron, XRP Ledger and Solana. Funds began leaving at 20:05 UTC on 29 Oct and the last Ethereum transfer finalised at 23:56 UTC. | 29 Oct | Binance suspended withdrawals, rebuilt the wallet system, replaced devices, decommissioned credentials and engaged independent security firms. It reports about 2.85 billion frozen or intercepted and 98% of impacted token assets replenished, verifiable on its Proof of Reserves page. Withdrawals reopened in phases from 1 Nov. Figures are subject to reconciliation and press totals differ slightly. | | Entry chain (Binance account) | June 2026: supply-chain compromise via a tampered Homebrew installation. September: social engineering of a software engineer through a fake job interview and a malicious assignment repository. 20 Oct: an internal AI tool used as a springboard. 29 Oct: access to a wallet engineer's computer using credentials stolen from a DevOps engineer, then unauthorised use of an internal wallet signing service. | Jun to 29 Oct | Self-reported by Binance on 3 Nov and described as a multi-stage campaign. Binance's first account (30 Oct) cited a compromised DevOps laptop. Independent researchers corroborate the fake-recruiter tactic but not every timeline step. Earlier press reports of preparation lasting only 36 hours are superseded by Binance's account of months. | | EIP-7702 delegation | Attacker used EIP-7702 to give an attacker-controlled contract partial execution rights over a hot wallet. Analysts (Elliptic, TRM) found 50 pre-signed authorisations in one Ethereum transaction and signing on other chains, indicating the attacker could make Binance's own systems sign. Binance's CEO said the use did not pass normal approval controls. The wallet used MPC, so removal needed a special revocation. | 29 to 30 Oct | Delegation on the Binance14 hot wallet revoked at 00:10 UTC on 30 Oct. No CVE: this was abuse of legitimate functionality plus compromised signing access. Attribution: Binance cites an FBI statement that North Korea is responsible; the FBI page itself was not readable for this briefing. | **Actions:** for any company or yacht holding crypto or signing authority, separate signing systems by wallet tier, require multi-person approval for large movements, alert on unexpected delegations or permission changes, restrict software installs on privileged devices, and keep a tested, pre-approved way to revoke access. Screen deposits against published attacker addresses. Priority 2 of 5 ## Deckies and crypto: what Binance teaches the crew Watch ### In plain English Deckhands are renowned for putting wages and tips into crypto and trading it from their phones, often over yacht Wi-Fi and sometimes on a shared laptop in the crew mess. That makes crew a natural target. The Binance theft shows how attackers think. They did not break the maths. They targeted people: a fake recruiter, a "coding test" and a tampered installer, then worked their way along from one trusted computer to the next until they reached access that could move everything at once. Crew are exactly the kind of people who get fake job offers, whether through a crewing platform, LinkedIn or a message from a "captain" with an attachment to open. Onboard the same pattern looks like one captain's laptop, one shared admin password, or one vendor login that can reach the whole network. For your personal crypto, the biggest risks are fake approval requests that hand control of your wallet to someone else, software installed from an unofficial source, and a recovery phrase kept in a photo or a cloud note. ### What to do - Treat unsolicited job approaches with suspicion. Check the recruiter and company independently, and never download or run a "test", "assignment" or document from someone you have not verified. - Keep crypto logins off shared crew PCs, bridge computers and yacht work devices. Use your own phone or laptop, kept up to date, and install apps only from official stores or the maker's own site. - Use a unique password and an authenticator app or passkey. Consider a hardware wallet for anything you plan to hold long term. - Never approve a wallet signing or permission request you do not understand, and never type your recovery phrase into a website or send it to "support". - Onboard: ask who has admin rights on the yacht's systems, whether any account is shared, and whether big changes need a second person to approve. - Contact IT support if unsure. \+Technical detail for your onboard technical person Tap to open / close ▾ | Reference | Issue | Date | Fix and status | | --- | --- | --- | --- | | Social engineering and untrusted software | Fake recruiter, fake video interviews and a malicious repository delivered malware that, per Binance, evaded endpoint security. A tampered package installer gave an earlier foothold. Onboard equivalents: crew job approaches, fake invoices or charter enquiries with attachments, and unofficial app installs. | Jun to Oct | Application allow-listing, no admin rights for daily use, verified software sources, and awareness briefings for crew. | | Single point of control | Stolen credentials and trust between internal tools let the attackers move laterally to the wallet signing system. Onboard equivalents: a captain or ETO laptop with saved admin sessions, a shared network admin login, or a remote support tool with standing access. | Ongoing | Named admin accounts, MFA, least privilege, and separate admin devices for critical systems. | | Delegated access | EIP-7702 lets a wallet hand control to another contract by signing an authorisation. Onboard equivalent: approving a vendor, app or remote tool that then acts with your authority. | Ongoing | Review third-party access and app permissions regularly and revoke what is not used. | **Actions:** list every admin and vendor account on the yacht's systems, remove shared logins, enforce MFA, keep a break-glass procedure, restrict installs on privileged devices, and brief crew on fake recruiters, crypto scams and phished approvals. Keep the guidance personal and security-focused. Whether to hold crypto at all is each person's own decision. Priority 3 of 5 ## The European fridge hacks Exploited Critical ### In plain English On the night of 11 October, attackers reached the control boxes that run supermarket fridges and freezers in France and switched them into defrost mode with the food still inside. Hundreds of stores were hit, with food spoiled and, in some cases, equipment melting or catching fire. Nothing sounded an alarm and many staff were not in. France's national cyber agency issued an alert the next day, and Intermarché's boss expected losses in the tens of millions of euros. On 2 November it happened again, this time in at least half a dozen countries including Belgium, Sweden, Ireland, Italy and Estonia, with a further case reported in Greece. In Sweden one store's fridges and freezers were set to 50 degrees. No one has claimed responsibility, authorities have not named anyone, and Paris prosecutors have opened an inquiry. What officials do say is that the controllers were connected straight to the internet. The UK's National Cyber Security Centre said they had default passwords, and a UK minister said known vulnerabilities were exploited. Danfoss says most affected systems were older products with no security updates, and Copeland points to discontinued controllers. The exact break-in method has not been officially confirmed. ### What to do - Ask your onboard technical person whether any fridge, freezer, cold room or wine room has a network connection, a web page or remote vendor access. - If the controller is from Danfoss, Copeland or Dixell, ask for its firmware version and for default passwords to be changed. - Make sure no cold-room controller can be reached from the internet. Access should be through a VPN or a vendor session approved and logged by the yacht. - A different make: check when it was last updated and whether the maker still supports it. - Contact IT support if unsure. \+Technical detail for your onboard technical person Tap to open / close ▾ | Reference | Issue | Date | Fix and status | | --- | --- | --- | --- | | CERTFR-2026-ALE-012 | CERT-FR alert on "numerous compromises" of remote refrigeration controllers: Danfoss AK-SM and AK-SC series, Copeland xweb and Dixell xweb. Management interfaces exposed to the internet. Reported effects: forced defrost cycles with stock inside, temperatures up to about 50 degrees C, some fires, no alarms. Alert versions: 12, 13 and 16 Oct. | 12 Oct (updated 16 Oct) | Remove internet exposure of all affected units, check the whole configuration including defrost schedules, restore access only through a secure VPN or protected network, update firmware, set Danfoss security level to Strict and change default passwords. A source-IP filter for contractors is an emergency measure only. If compromised, restart or factory reset, reconfigure, apply fixes and change secrets, but a factory reset alone is not enough. CERT-FR warns campaigns are probably still ongoing and that exposed end-of-life equipment is very likely to be compromised. The alert lists no CVE IDs. | | CVE-2025-41450 CVE-2025-41451 CVE-2025-41452 | Danfoss AK-SM 800A authentication bypass, command injection and denial of service (Claroty Team82). Press reports a "code of the day" date-based login. Authorities and Danfoss have not publicly linked these CVEs to the attacks. Related: Copeland XWEB Pro CVE-2026-25085 and CVE-2026-21718 (23 flaws in total, patched in firmware 1.13). | Disclosed 2025 (Copeland: 2026) | AK-SM 800A: R4.3.1 or later (sources differ on the fix version for the first CVE). A 3.x system should move to 4.x first, and a controller on 5.3.x cannot be downgraded. AK-SC355 reached end of life in 2016 and AK-SM800 in 2021 with no updates. Secondary reporting: check Danfoss and Copeland advisories directly. | | Second wave | Overnight into 2 Nov: stores in Belgium, Luxembourg, Sweden, Ireland, Italy, Estonia, plus the Netherlands, Finland and Portugal in other reports. Methods: defrost mode or raised setpoints. In Estonia an old, un-updated Danfoss system was hit but only 2 to 3 degrees of warming occurred. A Belgian butcher lost about 15,000 euros of meat. An Athens butcher reported a unit set to 150 degrees (owner's claim, unverified). The EU Commission says the incidents are "not isolated". Darktrace says there is no evidence AI was used. | 2 to 3 Nov | Same mitigations as above. Danfoss told Dutch customers to disconnect and reconnect only through a secure network. The link between the two waves is not established, and no attribution has been made. | **Actions:** identify every refrigeration or HVAC controller with a network port, confirm it is not reachable from the internet, record firmware and support status, and replace end-of-life units. Store counts and costs vary widely between sources (for example 150 to 300 or more Intermarché and Netto stores), so no single figure is quoted. Reports linking US military commissary outages are unconfirmed. None of the sources read mention ships or yachts, so the onboard relevance here is by analogy. Priority 4 of 5 ## It is not just the fridge: other critical systems and safety Watch ### In plain English A fridge is the easy example because the loss is easy to picture: a cold room of wagyu, seafood and vintage wine quietly warmed overnight. But the fridge is just one example of operational technology (OT), the equipment that runs the physical yacht. Air conditioning and chillers, power and generator controls, engine room and tank monitoring, fire and bilge alarms, ventilation, lighting and AV control, stabilisers and thrusters all rely on small controllers that are often connected to the yacht network and often maintained remotely by the maker. If the controller can be reached and its settings changed, the screen on the wall can show one thing while the equipment does another. This is a safety issue as well as a financial one. In the French attacks, forced defrost cycles reportedly melted equipment and started fires, and no alarm went off. Onboard, that could mean overheating machinery in an enclosed space, silenced or false alarms, spoiled food that makes people ill, or loss of power or propulsion at the wrong moment. We know the last one is not theoretical. Some years ago a yacht manoeuvring in port went dead ship after a remote update to onboard fridge equipment. That was not an attack, but it shows how a remote change to "just a fridge" can reach vital systems. None of the reports we read mention a yacht being hit, so treat this as a lesson by analogy, but earlier CyIntel briefings have covered real flaws in systems found on yachts, including industrial controllers, building automation and ship operations software. ### What to do - Ask your onboard technical person for a list of every control system with a network port or remote vendor access, and mark which ones affect safety: fire, flooding, power, propulsion, steering, ventilation. - Make sure safety alarms are independent: hard-wired or on their own battery and alert route, not reliant on the controller they monitor. - Practise the manual fallback for critical plant, so the crew can run it without the screen. Check by hand when something looks wrong, for example with a probe thermometer or by looking at the equipment. - Ask that vendor remote access is off by default, approved per session and logged, and that no remote updates run while manoeuvring, in port, or during a critical power change. - Contact IT support if unsure, and report any equipment behaving oddly even if the alarm is quiet. \+Technical detail for your onboard technical person Tap to open / close ▾ | Reference | Issue | Date | Fix and status | | --- | --- | --- | --- | | Galley, cold rooms and wine rooms | Same exposure as the French supermarkets: web-managed refrigeration controllers, default credentials, unsupported firmware. Impact: spoilage, food safety, heat damage and fire risk. | Oct to Nov | See Priority 3 and 5. Independent logging and alarm, VPN-only access. | | HVAC, chillers and ventilation | Building and HVAC controllers share the same remote-management pattern. Altered setpoints can overheat equipment rooms or affect guest areas. Related earlier CyIntel item: KNX building automation flaws (July). | Ongoing | Segment building and HVAC systems, remove inbound internet, change default passwords, review setpoints against a known-good baseline. | | Power, alarm and monitoring systems, PLCs | Industrial controllers sit behind engine room, tank, bilge and alarm monitoring on many vessels. Earlier CyIntel items: a joint NSA and CISA advisory (AA26-231A, August) on attacks against internet-exposed Siemens S7 PLCs used in vessel automation, Wartsila FOS-Onboard hard-coded keys (September) and Lantronix serial device servers (August). | Aug to Sep | Follow the vendor and advisory guidance in those issues. Keep PLCs and serial gateways off the internet, isolate OT from crew and guest networks, and keep hard-wired safety trips independent of networked control. | | Remote vendor updates | An accidental example: a remote update to fridge equipment contributed to a yacht going dead ship while manoeuvring in port. The same risk applies to any controller on shared power or network infrastructure. | Years ago | Change control for every remote update, named approver, no updates during manoeuvring, port approach or critical power changes, and a tested rollback. | **Actions:** build an OT asset inventory with network path, vendor access, firmware and support status, and a safety rating for each system. Segment OT from IT, crew and guest networks. Replace unsupported controllers, require MFA and named accounts for vendor access, and test manual operation and alarm independence. For new builds, class rules (IACS UR E26 and E27) treat this as a core safety requirement. Confirm exact obligations with your class society. Priority 5 of 5 ## Protecting the galley and the provisions Watch ### In plain English The galley is where the lesson is easiest to see, so it is a good place to start. A provision store stocked for an owner's trip can hold tens of thousands of euros of premium food and wine, and a quiet overnight change to a cold-room controller could ruin it without a single alarm. It also shows the wider point: if the alarm depends on the same controller the attacker changed, it will say everything is fine. ### What to do - Fit an independent temperature logger or alarm on its own battery and alert route, not tied to the fridge controller. - Check temperatures with a separate probe thermometer as part of the daily galley routine, not only the controller display. - Agree a plan for high-value stock: a second cold space, ice or a rapid transfer route, and who decides. - Do not serve food from a unit that may have warmed, even if it looks fine. Follow your food safety procedures. - Check insurance wording for spoilage and for cyber causes, and contact IT support if unsure. \+Technical detail for your onboard technical person Tap to open / close ▾ | Reference | Issue | Date | Fix and status | | --- | --- | --- | --- | | Galley and cold-room controllers | Internet-reachable or vendor-managed controllers, default credentials, unsupported firmware, and alarms that depend on the compromised controller. | Ongoing | Segment galley equipment on its own VLAN with no inbound internet, VPN-only vendor access, independent monitoring and out-of-band alerts. | **Actions:** inventory every refrigeration controller and its network path, remove public exposure, change default passwords, update or replace end-of-life units, and review defrost schedules and setpoints against a known-good baseline. Add an independent alarm with an out-of-band alert, document a spoilage response plan, and require a named approver for any remote vendor session or update. ### How we rate items **Exploited.** The vendor or CISA's Known Exploited Vulnerabilities list confirms attacks in the wild. For these two incidents, the attacks are confirmed by the affected companies, authorities and the reporting we read. **Critical.** The vendor or CVSS rates it critical. This says nothing about whether attacks are happening. **Watch.** No confirmed attacks, but the item is on kit that matters, or no fix exists. **Sources.** Binance's own incident post (3 November 2026) and the French CERT-FR alert CERTFR-2026-ALE-012 were read directly. Supporting reporting: TRM Labs, Elliptic, CoinDesk, TechCrunch and Finchannel on Binance; The Hacker News, the Associated Press, Fortune, Cybersecurity Dive and the Cloud Security Alliance on the fridge attacks. The onboard systems section draws on earlier CyIntel briefings (CISA and NSA advisory AA26-231A and vendor advisories) and is an analogy, since no source read reports an attack on a yacht. The FBI alert on Binance (as quoted by Binance), the Danfoss and Copeland advisories, and the NPR, NBC, CNN and CNBC pages could not be read directly. Where reports disagree we say so. This briefing is a snapshot as of 5 November 2026. Details, including figures and the cause of the fridge attacks, can change, so check the sources before acting. [**Click here to join our Cybersecurity Threat Intelligence WhatsApp Group for Superyacht Crew - CyIntel.**](https://chat.whatsapp.com/HYSx9cqcLqPF42iftYw2zt?mode=gi_t) --- Welcome to our bi-weekly cyber briefing for superyacht crew, where I share some of the major developments, lessons learned and helpful guides to help you improve onboard cybersecurity. Make sure to [**follow my LinkedIn page**](https://www.linkedin.com/in/superyachtcybersecurity/) and [**Anchorpoint's LinkedIn page**](https://www.linkedin.com/company/trustanchorpoint/) to receive updates on the future of superyacht cybersecurity! To receive these and other curated updates to your inbox on a regular basis, please sign up for our email [**by clicking here**](https://2f009r.share-eu1.hsforms.com/2vmZv2EFcTRq5KwDy93Wwzw). ## Share this post [mailto:https%3A%2F%2Ftrustanchorpoint.com%2Finsights%2Fsuperyacht-cyber-intelligence-special-binance-and-the-fridge-hacks](mailto:https%3A%2F%2Ftrustanchorpoint.com%2Finsights%2Fsuperyacht-cyber-intelligence-special-binance-and-the-fridge-hacks) ## Keep reading ### [![](https://trustanchorpoint.com/hs-fs/hubfs/Cover-1.png?width=1920&height=1080&name=Cover-1.png) Superyacht Cyber Intelligence: Remote Access Gateways Under Attack (Issue #019)](https://trustanchorpoint.com/insights/superyacht-cyber-intelligence-remote-access-gateways-under-attack-issue-20) ### [![](https://trustanchorpoint.com/hs-fs/hubfs/Cover.png?width=1920&height=1080&name=Cover.png) Cyber security Cybersecurity Superyachts Superyacht Cyber Intelligence: Onboard Firewall Flaws Under Attack (Issue #018)](https://trustanchorpoint.com/insights/superyacht-cyintel-briefing-7-october-2026) [![L-White-White-Tran](https://trustanchorpoint.com/hs-fs/hubfs/L-White-White-Tran.png?width=200&height=56&name=L-White-White-Tran.png "L-White-White-Tran")](https://www.trustanchorpoint.com) - [Privacy Policy](https://trustanchorpoint.com/hubfs/Privacy%20Policy.pdf) - [Terms & Conditions](https://trustanchorpoint.com/hubfs/Terms%20and%20Conditions.pdf) - [Contact Us](https://trustanchorpoint.com/contact) - [Climate Pledge](https://climate.stripe.com/hLNMmV) © 2026 Anchorpoint (trading name of Anchorpoint Cyber Limited). Company number 16320713, registered in England. All rights reserved. ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Matt", "url" : "https://trustanchorpoint.com/insights/author/matt" }, "dateModified" : "2026-11-05T11:19:34.975Z", "datePublished" : "2026-11-05T11:18:39.000Z", "headline" : "Superyacht Cyber Intelligence Special: Binance and the Fridge Hacks", "mainEntityOfPage" : { "@id" : "https://trustanchorpoint.com/insights/superyacht-cyber-intelligence-special-binance-and-the-fridge-hacks", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://trustanchorpoint.com/hubfs/Black-White.png" }, "name" : "Anchorpoint Cyber Limited" } } ```