Comparison Overview

Empire Auto Parts

VS

A.P. Moller - Maersk

Empire Auto Parts

15 Jackson Road, None, Totowa, NJ, US, 07512
Last Update: 2025-07-26 (UTC)
Between 700 and 749

Empire Auto Parts is the fastest growing supplier of aftermarket automotive collision and cooling parts in the United States, with 46 locations across 26 states from Maine to Texas. We stock over 800,000 parts in inventory from 675 vehicle makes, models and vintages. Here’s how we do it: PRODUCT QUALITY Quality control begins at the factory, where Empire is directly involved in production, packaging, and shipment decisions that ensure unmatched part quality levels, whether parts are CAPA certified or non-certified. As a result, our quality-based return rates are ¼ the industry average. SERVICE We provide daily delivery from Empire employees in company vans to ensure that your parts are treated with the same care that you give to the vehicle you are repairing for YOUR customer. Our parts are covered by the best warranty in the industry. And if you need help, just call one of our highly-skilled representatives located in your region to assist you. We make doing business with Empire easy. CHOICE We want you to order parts in a manner that works best for your business, not ours. So if you utilize an electronic procurement platform like CCC, OPS, PartsTrader or others, we are fully integrated to make ordering easy. If you prefer to use our proprietary web portal, we have that option. Or you can call us on the phone and we can handle your order that way. So whether you are a single location repair shop in a small town or one of the nation’s largest multi-shop operators, we have what you need: A/C Condensers Bumpers & Components Cameras & Sensors Coolant & Washer Fluid Tanks Cooling Fans Doors Door Handles Door Mirrors Fenders & Fender Liners Grilles & Components Header & Nose Panels Headlamp Doors Hoods, Hinges & Supports Inner Structures Lamps & Components Pads & Moldings Radiators Radiator Supports Rust Repair Panels Tailgates Trunk Lids Window Regulators Contact us. We would love to work together.

NAICS: 47
NAICS Definition: Transportation and Warehousing
Employees: 317
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

A.P. Moller - Maersk

Esplanaden 50, None, Copenhagen, None, DK, 1098
Last Update: 2025-08-04 (UTC)
Between 750 and 799

A.P. Moller - Maersk is an integrated transport and logistics company; going all the way, together, for our customers and society. ALL THE WAY is our commitment to connect the world so that everyone has both the possibility and the ability to trade, grow and thrive. The company employs roughly 110.000 employees across operations in 130 countries.

NAICS: 47
NAICS Definition: Transportation and Warehousing
Employees: 79,448
Subsidiaries: 17
12-month incidents
1
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/empire-auto-parts.jpeg
Empire Auto Parts
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/maersk-group.jpeg
A.P. Moller - Maersk
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Empire Auto Parts
100%
Compliance Rate
0/4 Standards Verified
A.P. Moller - Maersk
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Average (This Year)

No incidents recorded for Empire Auto Parts in 2025.

Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Average (This Year)

A.P. Moller - Maersk has 28.21% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Empire Auto Parts (X = Date, Y = Severity)

Empire Auto Parts cyber incidents detection timeline including parent company and subsidiaries

Incident History — A.P. Moller - Maersk (X = Date, Y = Severity)

A.P. Moller - Maersk cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/empire-auto-parts.jpeg
Empire Auto Parts
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Email Account Compromise
Blog: Blog
https://images.rankiteo.com/companyimages/maersk-group.jpeg
A.P. Moller - Maersk
Incidents

Date Detected: 8/2025
Type:Cyber Attack
Attack Vector: Compromised Software Updates (NotPetya via Ukrainian accounting software), Phishing/Social Engineering, Outdated/Poorly Maintained Systems, Third-Party Vendor Vulnerabilities, GNSS Jamming/Spoofing (Russia, Iran, China), AI-Assisted Exploits (e.g., subverting AI assistants), Manual Override of Digital Systems (human error)
Motivation: Financial Gain (Ransomware), Geopolitical Disruption (State Actors), Espionage (Strategic Maritime Data), Hacktivism (e.g., Lab-Dookhtegan), Operational Sabotage (e.g., GNSS Interference)
Blog: Blog

Date Detected: 6/2017
Type:Cyber Attack
Attack Vector: Malware (NotPetya), Supply Chain Compromise (via Ukrainian accounting software M.E.Doc), Lateral Movement
Motivation: Geopolitical (targeting Ukraine), Collateral Damage (global spread), Disruption of Critical Infrastructure
Blog: Blog

Date Detected: 6/2017
Type:Cyber Attack
Attack Vector: Compromised Software Update, Backdoor in M.E.Doc
Motivation: Geopolitical Disruption, Targeting Ukraine (Maersk as collateral damage)
Blog: Blog

FAQ

A.P. Moller - Maersk company demonstrates a stronger AI Cybersecurity Score compared to Empire Auto Parts company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

A.P. Moller - Maersk company has faced a higher number of disclosed cyber incidents historically compared to Empire Auto Parts company.

In the current year, A.P. Moller - Maersk company has reported more cyber incidents than Empire Auto Parts company.

Neither A.P. Moller - Maersk company nor Empire Auto Parts company has reported experiencing a ransomware attack publicly.

Empire Auto Parts company has disclosed at least one data breach, while the other A.P. Moller - Maersk company has not reported such incidents publicly.

A.P. Moller - Maersk company has reported targeted cyberattacks, while Empire Auto Parts company has not reported such incidents publicly.

Neither Empire Auto Parts company nor A.P. Moller - Maersk company has reported experiencing or disclosing vulnerabilities publicly.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds any compliance certifications.

Neither company holds any compliance certifications.

A.P. Moller - Maersk company has more subsidiaries worldwide compared to Empire Auto Parts company.

A.P. Moller - Maersk company employs more people globally than Empire Auto Parts company, reflecting its scale as a Transportation, Logistics, Supply Chain and Storage.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds SOC 2 Type 1 certification.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds SOC 2 Type 2 certification.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds ISO 27001 certification.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds PCI DSS certification.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds HIPAA certification.

Neither Empire Auto Parts nor A.P. Moller - Maersk holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Deck Mate 1 executes firmware directly from an external EEPROM without verifying authenticity or integrity. An attacker with physical access can replace or reflash the EEPROM to run arbitrary code that persists across reboots. Because this design predates modern secure-boot or signed-update mechanisms, affected systems should be physically protected or retired from service. The vendor has not indicated that firmware updates are available for this legacy model.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Deck Mate 2's firmware update mechanism accepts packages without cryptographic signature verification, encrypts them with a single hard-coded AES key shared across devices, and uses a truncated HMAC for integrity validation. Attackers with access to the update interface - typically via the unit's USB update port - can craft or modify firmware packages to execute arbitrary code as root, allowing persistent compromise of the device's integrity and deck randomization process. Physical or on-premises access remains the most likely attack path, though network-exposed or telemetry-enabled deployments could theoretically allow remote exploitation if misconfigured. The vendor confirmed that firmware updates have been issued to correct these update-chain weaknesses and that USB update access has been disabled on affected units.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Uncontrolled Resource Consumption vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS bc-fips on All (API modules), Legion of the Bouncy Castle Inc. Bouncy Castle for Java LTS bcprov-lts8on on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCFB.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeGCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/SHA256NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeEngine.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCBC.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCTR.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCFB.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeGCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeEngine.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCBC.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeGCMSIV.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCTR.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA256NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA224NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA3NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHAKENativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA512NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA384NativeDigest.Java. This issue affects Bouncy Castle for Java FIPS: from 2.1.0 through 2.1.1; Bouncy Castle for Java LTS: from 2.73.0 through 2.73.7.

Risk Information
cvss4
Base: 5.9
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:U/V:C/RE:M/U:Amber
Description

Wasmtime is a runtime for WebAssembly. In versions from 38.0.0 to before 38.0.3, the implementation of component-model related host-to-wasm trampolines in Wasmtime contained a bug where it's possible to carefully craft a component, which when called in a specific way, would crash the host with a segfault or assert failure. Wasmtime 38.0.3 has been released and is patched to fix this issue. There are no workarounds.

Risk Information
cvss4
Base: 2.1
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X