Comparison Overview

Takeda

VS

Eli Lilly and Company

Takeda

Tokyo, JP
Last Update: 2026-01-18
View Profile
Between 800 and 849
https://www.takeda.com/

We strive to transform lives. While the science we advance is constantly evolving, our core purpose is enduring. For more than two centuries, our values have guided us to do what’s right for patients and for society. We know that changing lives requires us to do things differently. We start by listening to and addressing what really matters to patients, the people who love them, and those in the healthcare system who provide care. And that’s what inspires us all to be bold, push boundaries and set new standards that open up greater opportunities. Read our community guidelines: https://takeda.info/communityguidelines

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 37,228
Subsidiaries: 6
12-month incidents
0
Known data breaches
1
Attack type number
1
View Profile

Eli Lilly and Company

Lilly Corporate Center, Indianapolis, Indiana, US, 46285
Last Update: 2026-01-17
Between 800 and 849
http://www.lilly.com/

We're a medicine company turning science into healing to make life better for people around the world. It all started nearly 150 years ago with a clear vision from founder Colonel Eli Lilly: "Take what you find here and make it better and better." Harnessing the power of biotechnology, chemistry and genetic medicine, our scientists are urgently advancing science to solve some of the world's most significant health challenges. General Information and Guidelines: When you engage with us on LinkedIn, you're agreeing to these Community Guidelines: https://e.lilly/guidelines. If you have questions about a Lilly medicine, contact The Lilly Answers Center at 1-800-Lilly-Rx (1-800-545-5979) Monday through Friday, excluding company holidays.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 53,748
Subsidiaries: 16
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
—
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/eli-lilly-and-company.jpeg
Eli Lilly and Company
—
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
Takeda
100%
Compliance Rate
0/4 Standards Verified
Eli Lilly and Company
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Takeda in 2026.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Eli Lilly and Company in 2026.

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

Takeda cyber incidents detection timeline including parent company and subsidiaries

Incident History — Eli Lilly and Company (X = Date, Y = Severity)

Eli Lilly and Company cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Credential Stuffing
Blog: Blog
https://images.rankiteo.com/companyimages/eli-lilly-and-company.jpeg
Eli Lilly and Company
Incidents

No Incident

FAQ

Eli Lilly and Company company demonstrates a stronger AI Cybersecurity Score compared to Takeda company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Takeda company has historically faced a number of disclosed cyber incidents, whereas Eli Lilly and Company company has not reported any.

In the current year, Eli Lilly and Company company and Takeda company have not reported any cyber incidents.

Neither Eli Lilly and Company company nor Takeda company has reported experiencing a ransomware attack publicly.

Takeda company has disclosed at least one data breach, while the other Eli Lilly and Company company has not reported such incidents publicly.

Neither Eli Lilly and Company company nor Takeda company has reported experiencing targeted cyberattacks publicly.

Neither Takeda company nor Eli Lilly and Company company has reported experiencing or disclosing vulnerabilities publicly.

Neither Takeda nor Eli Lilly and Company holds any compliance certifications.

Neither company holds any compliance certifications.

Eli Lilly and Company company has more subsidiaries worldwide compared to Takeda company.

Eli Lilly and Company company employs more people globally than Takeda company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither Takeda nor Eli Lilly and Company holds SOC 2 Type 1 certification.

Neither Takeda nor Eli Lilly and Company holds SOC 2 Type 2 certification.

Neither Takeda nor Eli Lilly and Company holds ISO 27001 certification.

Neither Takeda nor Eli Lilly and Company holds PCI DSS certification.

Neither Takeda nor Eli Lilly and Company holds HIPAA certification.

Neither Takeda nor Eli Lilly and Company holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

Published
Date
2026-01-23
Updated
Date
2026-01-23
Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
References
Description

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Published
Date
2026-01-23
Updated
Date
2026-01-23
References
Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Published
Date
2026-01-23
Updated
Date
2026-01-23
References
Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Published
Date
2026-01-23
Updated
Date
2026-01-23
Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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
References
Description

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.

Published
Date
2026-01-23
Updated
Date
2026-01-23
References