Comparison Overview

iMesh

VS

DoorDash

iMesh

Last Update: 2025-12-09
Between 700 and 749

iMesh is a media and file sharing client that's available in 9 languages. It uses a proprietary, centralized, P2P network (IM2Net) operating on ports 80, 443 and 1863.[1] iMesh is owned by American company iMesh, Inc. and maintains development centers around the world. It is the 3rd most popular music subscription service in the US.[2] iMesh operates the first "RIAA-approved"​ P2P service, allowing users residing in United States and Canada to download music content of choice for a monthly fee in the form of either a Premium subscription or a "ToGo"​ subscription. This subscription based approach is advocated by theories such as the Open Music Model. A third option is also available for users (residing in either country) to permanently purchase tracks for 0.99 USD each, without a subscription.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 13
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

DoorDash

San Francisco, California, US
Last Update: 2025-12-11

At DoorDash, our mission to empower local economies shapes how our team members move quickly and always learn and reiterate to support merchants, Dashers and the communities we serve. We are a technology and logistics company that started with door-to-door delivery, and we are looking for team members who can help us go from a company that is known for delivering food to a company that people turn to for any and all goods. DoorDash is growing rapidly and changing constantly, which gives our team members the opportunity to share their unique perspectives, solve new challenges, and own their careers. Our leaders seek the truth and welcome big, hairy, audacious questions. We are grounded in our company values, and we make intentional decisions that are both logical and display empathy for our range of users—from Dashers to Merchants to Customers.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 74,124
Subsidiaries: 2
12-month incidents
3
Known data breaches
9
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/imesh.jpeg
iMesh
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/doordash.jpeg
DoorDash
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
iMesh
100%
Compliance Rate
0/4 Standards Verified
DoorDash
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for iMesh in 2025.

Incidents vs Software Development Industry Average (This Year)

DoorDash has 417.24% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — iMesh (X = Date, Y = Severity)

iMesh cyber incidents detection timeline including parent company and subsidiaries

Incident History — DoorDash (X = Date, Y = Severity)

DoorDash cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/imesh.jpeg
iMesh
Incidents

Date Detected: 6/2016
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/doordash.jpeg
DoorDash
Incidents

Date Detected: 11/2025
Type:Breach
Attack Vector: Third-Party Vendor Compromise, Credential Theft, Social Engineering
Motivation: Data Theft, Potential Fraud Enablement
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Social Engineering (Employee Targeted)
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Social Engineering, Phishing (Spear Phishing/Vishing), Compromised Credentials
Motivation: Data Theft for Follow-on Attacks (e.g., Spear Phishing, Vishing), Potential Financial Gain via Stolen Data
Blog: Blog

FAQ

iMesh company demonstrates a stronger AI Cybersecurity Score compared to DoorDash company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

DoorDash company has faced a higher number of disclosed cyber incidents historically compared to iMesh company.

In the current year, DoorDash company has reported more cyber incidents than iMesh company.

Neither DoorDash company nor iMesh company has reported experiencing a ransomware attack publicly.

Both DoorDash company and iMesh company have disclosed experiencing at least one data breach.

Neither DoorDash company nor iMesh company has reported experiencing targeted cyberattacks publicly.

DoorDash company has disclosed at least one vulnerability, while iMesh company has not reported such incidents publicly.

Neither iMesh nor DoorDash holds any compliance certifications.

Neither company holds any compliance certifications.

DoorDash company has more subsidiaries worldwide compared to iMesh company.

DoorDash company employs more people globally than iMesh company, reflecting its scale as a Software Development.

Neither iMesh nor DoorDash holds SOC 2 Type 1 certification.

Neither iMesh nor DoorDash holds SOC 2 Type 2 certification.

Neither iMesh nor DoorDash holds ISO 27001 certification.

Neither iMesh nor DoorDash holds PCI DSS certification.

Neither iMesh nor DoorDash holds HIPAA certification.

Neither iMesh nor DoorDash holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A weakness has been identified in itsourcecode Online Pet Shop Management System 1.0. This vulnerability affects unknown code of the file /pet1/addcnp.php. This manipulation of the argument cnpname causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be exploited.

Risk Information
cvss2
Base: 7.5
Severity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

A security flaw has been discovered in Tenda AX9 22.03.01.46. This affects the function image_check of the component httpd. The manipulation results in use of weak hash. It is possible to launch the attack remotely. A high complexity level is associated with this attack. It is indicated that the exploitability is difficult. The exploit has been released to the public and may be exploited.

Risk Information
cvss2
Base: 2.6
Severity: HIGH
AV:N/AC:H/Au:N/C:N/I:P/A:N
cvss3
Base: 3.7
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
cvss4
Base: 6.3
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

A weakness has been identified in code-projects Student File Management System 1.0. This issue affects some unknown processing of the file /admin/update_student.php. This manipulation of the argument stud_id causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

Risk Information
cvss2
Base: 7.5
Severity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

A security flaw has been discovered in code-projects Student File Management System 1.0. This vulnerability affects unknown code of the file /admin/save_user.php. The manipulation of the argument firstname results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be exploited.

Risk Information
cvss2
Base: 7.5
Severity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

A vulnerability was identified in code-projects Student File Management System 1.0. This affects an unknown part of the file /admin/update_user.php. The manipulation of the argument user_id leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used.

Risk Information
cvss2
Base: 7.5
Severity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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