Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
OpenSearch Project

OpenSearch Project Vendor Cyber Rating & Cyber Score

opensearch.org

OpenSearch is the trusted vendor-neutral open source platform for AI-powered search, analytics, observability, and vector database solutions. Built for scalability, performance, and extensibility, developers and enterprises rely on OpenSearch to securely manage workloads, without costly licensing. Hosted by the Linux Foundation and backed by the Apache 2.0-license, the OpenSearch platform offers transparent governance, freedom from vendor lock-in, and community-driven innovation.


OpenSearch Project A.I CyberSecurity Scoring

OpenSearch Project
Company Information
Website:https://opensearch.org/
Employees number:120
Number of followers:9,731
NAICS:5112
Industry Type:Software Development
Homepage:opensearch.org
OpenSearch Project Risk Score (AI oriented)
Between 550 and 599
logo
OpenSearch ProjectSoftware Development
Updated:
29/05/2026
592/1000
Very Poor
Ca
AaaAaABaaBaBCaaCaC
Powered by our proprietary A.I cyber incident model
Insurance prefers TPRM score to calculate premium
OpenSearch Project Global Score (TPRM)
xxxx
logo
OpenSearch ProjectSoftware Development
•••
Score locked
Instant access to detailed risk factors
Vulnerabilities
Benchmark vs. industry & size peers
Findings

OpenSearch Project
OpenSearch ProjectVery Poor
Current Score
592Ca (VERY POOR)
01000
3 incidents
-53 avg impact
Incident timeline with MITRE ATT&CK tactics, techniques, and mitigations.
JULY 2026
598Before Incident
JUNE 2026
595Before Incident
MAY 2026
613Before Incident
Cyber Attack
28 May 2026OpenSearch Project
OpenSearch, npm, ElasticSearch, Amazon Web Services and GitHub: Typosquatted npm Packages Steal Cloud and CI/CD Secrets

Sophisticated npm Supply Chain Attack Targets OpenSearch, ElasticSearch, and DevOps Tools

592After Incident
CRITICAL-21
ELAGITAMAOPENPM1780050263
Sophisticated npm Supply Chain Attack Targets OpenSearch, ElasticSearch, and DevOps Tools A recently uncovered npm supply chain attack has targeted developers working with OpenSearch, ElasticSearch, and DevOps tooling, stealing cloud credentials and CI/CD secrets from compromised systems. The campaign, attributed to a threat actor using the alias vpmdhaj, involved 14 malicious packages published on May 28, 2026, within a four-hour window. The attackers employed typosquatting and metadata spoofing, mimicking legitimate libraries with names like opensearch-setup and elastic-opensearch-helper while falsely linking to the official OpenSearch GitHub repository. To appear credible, the packages were assigned inflated version numbers, suggesting maturity and widespread use. Upon installation, the malicious packages executed code via npm preinstall scripts, triggering automatically without user interaction. The attack employed a two-stage payload system: - Early versions used a JavaScript stager to collect system details (hostname, OS, Node.js version, environment variables) and send them to a command-and-control (C2) server. The server responded with a compressed binary payload, identifiable by the “X-Supply: 1” HTTP header in network logs. - Later variants improved stealth by eliminating direct C2 communication, instead downloading the Bun runtime from GitHub to execute an embedded second-stage payload. This reduced suspicious outbound traffic and evaded traditional detection. The second-stage payload, a Bun-compiled binary, targeted credentials across multiple platforms, including: - Amazon Web Services (AWS) – Extracting environment variables, querying EC2 Instance Metadata Service and ECS task metadata, and enumerating secrets in AWS Secrets Manager. - HashiCorp Vault – Harvesting tokens. - GitHub Actions & npm – Validating publish tokens to hijack package maintainers and propagate further supply chain attacks. A persistence mechanism ensured the payload re-executed whenever the malicious module was imported, allowing it to survive across development cycles and CI/CD pipeline runs. The impact of the campaign is severe: - Stolen AWS credentials could enable lateral movement in cloud environments. - Compromised CI/CD tokens may allow attackers to manipulate build pipelines or inject malicious code into production. - Hijacked npm publish tokens pose a risk of malicious updates to legitimate packages, expanding the attack’s reach. Following responsible disclosure, the malicious packages and associated accounts were removed from the npm registry. However, organizations that installed these dependencies remain at risk. Security teams are urged to audit systems for affected packages, rotate exposed credentials, and monitor for indicators of compromise, including the “X-Supply: 1” header and unusual CloudTrail activity. The incident underscores the growing sophistication of supply chain attacks, where trusted ecosystems like npm are exploited to gain access to sensitive cloud and development infrastructure.
INCIDENT DETAILS -
TYPE
Supply Chain Attack
MOTIVATION
Credential TheftSupply Chain Compromise
IMPACT
Cloud credentialsCI/CD secretsAWS secretsHashiCorp Vault tokensGitHub Actions tokensnpm publish tokensDevelopment environmentsCI/CD pipelinesCloud infrastructure (AWS)Operational Impact: Potential lateral movement in cloud environments, manipulation of build pipelines, injection of malicious code into production
DATA BREACH
Cloud credentialsCI/CD secretsAWS secretsHashiCorp Vault tokensGitHub Actions tokensnpm publish tokensSensitivity Of Data: High
MAY 2026
752Before Incident
Breach
12 May 2026OpenSearch Project
Guardrails AI, TanStack, OpenSearch, React Router, Mistral AI and UiPath: 84 npm Packages Linked to TanStack Hit by Supply-Chain Breach

Massive Supply Chain Breach Hits 84 npm Packages in TanStack Ecosystem

689After Incident
CRITICAL-63
MISUIPOPETANGUA1778567093
Massive Supply Chain Breach Hits 84 npm Packages in TanStack Ecosystem A sophisticated supply chain attack compromised 84 npm packages within the widely used TanStack ecosystem, including high-profile libraries like React Router (12M+ weekly downloads). The breach, part of the Mini Shai-Hulud malware campaign, targeted continuous integration (CI) environments such as GitHub Actions, injecting a credential-stealing tool designed to evade detection. Security firm Socket detected the malicious packages within six minutes of publication using an AI-powered scanner. The attack extended beyond npm, infecting Python packages like OpenSearch, Mistral AI, Guardrails AI, and UiPath. A message left by the attackers signed TeamPCP confirmed they had been exfiltrating developer credentials for hours during the investigation. ### Attack Mechanics The malware, embedded in an obfuscated script (router_init.js), acted as a self-propagating worm. Key tactics included: - Stealth Execution: Detached from terminal sessions, running silently in the background. - Credential Harvesting: Targeted GitHub Actions tokens, AWS metadata, Kubernetes certificates, and HashiCorp Vault clusters. - Persistence: Hid copies in VS Code and Claude AI config directories, ensuring reinfection on workspace reopening. - Exfiltration: Used the Session peer-to-peer network to blend stolen data with encrypted messaging traffic. The attack leveraged a malicious `optionalDependencies` block in package.json, pointing to a compromised GitHub commit. During `npm install`, a `prepare` lifecycle hook executed tanstack_runner.js, triggering the payload. ### Chained GitHub Actions Exploit TanStack’s postmortem revealed the breach stemmed from a chained attack on their GitHub Actions pipeline. Attackers exploited a vulnerable pull request target pattern, poisoning the workflow cache to execute malicious code. Instead of stealing static npm tokens, they extracted runtime OpenID Connect tokens from runner memory, enabling legitimate authentication to push compromised updates. ### Response & Indicators of Compromise (IOCs) TanStack deprecated affected versions, purged workflow caches, and implemented stricter repository protections. Key IOCs include: - Malicious Files: - `router_init.js` (SHA256: `ab4fcadaec49c03278063dd269ea5eef82d24f2124a8e15d7b90f2fa8601266c`) - `tanstack_runner.js` (SHA256: `2ec78d556d696e208927cc503d48e4b5eb56b31abc2870c2ed2e98d6be27fc96`) - Network Targets: - `hxxp://filev2[.]getsession[.]org/file/` (Session P2P exfiltration) - AWS metadata endpoints (`169.254.169.254`, `169.254.170.2`) - GitHub API (`api.github.com/repos/`) and npm token validation endpoints.
INCIDENT DETAILS -
TYPE
Supply Chain Attack
MOTIVATION
Credential harvesting, data exfiltration
IMPACT
Data Compromised: GitHub Actions tokens, AWS metadata, Kubernetes certificates, HashiCorp Vault clusters, developer credentialsSystems Affected: CI/CD pipelines (GitHub Actions), npm packages, Python packages (OpenSearch, Mistral AI, Guardrails AI, UiPath)Operational Impact: Compromised software supply chain, potential reinfection via config directoriesBrand Reputation Impact: High (affected widely used libraries like React Router)Identity Theft Risk: High (developer credentials and PII exfiltration)
DATA BREACH
GitHub Actions tokensAWS metadataKubernetes certificatesHashiCorp Vault clustersDeveloper credentialsSensitivity Of Data: High (authentication tokens, infrastructure secrets)Data Exfiltration: Yes (via Session P2P network)Personally Identifiable Information: Developer credentials
MAY 2026
752Before Incident
Breach
01 May 2026OpenSearch Project
Mistral AI: Hackers threaten to leak Mistral files online — AI giant confirms breach, but not what data is involved

Mistral AI Suffers Data Breach: 450 Repositories Stolen and Auctioned on Dark Web

677After Incident
CRITICAL-75
MIS1778869722
Mistral AI Suffers Data Breach: 450 Repositories Stolen and Auctioned on Dark Web The hacking group TeamPCP has stolen 450 internal repositories totaling 5GB of source code from Mistral AI, a leading AI development company. The stolen data, which includes code used for training, fine-tuning, benchmarking, and model delivery, is now being auctioned on the dark web for $25,000. TeamPCP, which previously executed a supply chain attack called Mini Shai-Hulud against the TanStack npm package (a widely used UI toolkit with 177 million weekly downloads), distributed infostealer malware to harvest developer credentials, cloud secrets, and SSH keys. The group claims the stolen Mistral AI data contains experimental and future project materials and has warned that if no buyer emerges within a week, they will leak the entire dataset for free. Mistral AI confirmed the breach, stating that attackers compromised a codebase management system and briefly contaminated some SDK packages. However, the company emphasized that core systems, hosted services, user data, and research environments remained unaffected. The auction is exclusive to a single buyer, with TeamPCP even inviting Mistral AI to purchase the data back. The group has indicated that the $25,000 price is negotiable. The incident highlights ongoing risks in AI development supply chains and the potential exposure of proprietary model training materials.
INCIDENT DETAILS -
TYPE
Data Breach
MOTIVATION
Financial gain (auctioning stolen data)
IMPACT
Data Compromised: 5GB of source code (450 repositories)Systems Affected: Codebase management system, SDK packagesOperational Impact: Brief contamination of SDK packagesBrand Reputation Impact: Potential reputational damage due to data breach and auction
DATA BREACH
Type Of Data Compromised: Source code (training, fine-tuning, benchmarking, model delivery, experimental/future projects)Number Of Records Exposed: 450 repositoriesSensitivity Of Data: High (proprietary AI model training materials)Data Exfiltration: Yes (auctioned on dark web)File Types Exposed: Source codePersonally Identifiable Information: None mentioned
APRIL 2026
752Before Incident
MARCH 2026
752Before Incident
FEBRUARY 2026
752Before Incident
JANUARY 2026
752Before Incident
DECEMBER 2025
752Before Incident
NOVEMBER 2025
752Before Incident
OCTOBER 2025
752Before Incident
SEPTEMBER 2025
752Before Incident
AUGUST 2025
752Before Incident

Frequently Asked Questions

?
What is the current A.I Rankiteo Cyber Score for OpenSearch Project ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in June 2026 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in May 2026 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in April 2026 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in March 2026 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in February 2026 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in January 2026 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in December 2025 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in November 2025 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in October 2025 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in September 2025 ?
?
What was OpenSearch Project's A.I Rankiteo Cyber Score in August 2025 ?
?
What is the average per-incident point impact on OpenSearch Project's A.I Rankiteo Cyber Score over the past 12 months ?
?
Where can I access detailed records of all cyber incidents associated with OpenSearch Project ?
?
Where can I find a summary of the A.I Rankiteo Risk Scoring methodology ?
?
Where can I view OpenSearch Project's profile page on Rankiteo ?
?
How accurate is the A.I Rankiteo Risk Scoring methodology ?