# GHSA-27f5-xjrr-q9ff: Malware in @opensearch-project/opensearch

> Attackers injected malicious code into specific OpenSearch npm package versions, allowing full system compromise upon installation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026

## What is GHSA-27f5-xjrr-q9ff?

GHSA-27f5-xjrr-q9ff is a vulnerability in @opensearch-project/opensearch, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

## Overview

The OpenSearch Project has sustained a security incident involving an external actor gaining force-push permissions within the project's CI infrastructure to embed malicious packages into four release versions of `@opensearch-project/opensearch`. Users are instructed to immediately take actions recommended in the **Remediation** section of this advisory.

## Affected Versions

**Package**: `@opensearch-project/opensearch`

| Version | Published (UTC) | Published (America/New_York) |
|---------|----------------|------------------------------|
| 3.5.3 | 2026-05-12T00:47:39Z | May 11, 2026, 8:47:39 PM EDT |
| 3.6.2 | 2026-05-12T00:29:34Z | May 11, 2026, 8:29:34 PM EDT |
| 3.7.0 | 2026-05-12T00:42:29Z | May 11, 2026, 8:42:29 PM EDT |
| 3.8.0 | 2026-05-12T00:43:54Z | May 11, 2026, 8:43:54 PM EDT |

## Remediation

Any computer that has these package versions installed or updated between 00:00 UTC 12 May 2026 (8:00 PM EDT 11 May 2026) and 10:00 UTC 12 May 2026 (6:00 AM EDT 12 May 2026) should be considered fully compromised. Steps should immediately be taken to prevent further compromise.

- **All secrets and keys** stored on that computer should be rotated immediately from an alternate system.
- The affected packages should be removed immediately, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## References

[GHSA-g7cv-rxg3-hmpx](https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx)
https://github.com/TanStack/router/issues/7383

## Which versions are affected by GHSA-27f5-xjrr-q9ff?

2 open source packages ship an affected version, including @opensearch-project/opensearch.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@opensearch-project/opensearch` | npm | All versions | None |
| `@opensearch-project/opensearch` | npm | All versions | None |

## How do I fix GHSA-27f5-xjrr-q9ff?

No fix has been published for GHSA-27f5-xjrr-q9ff yet. Limit exposure of the affected software until one is available.

## Is GHSA-27f5-xjrr-q9ff being exploited?

There is no known exploitation of GHSA-27f5-xjrr-q9ff in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-27f5-xjrr-q9ff and fix it if it is affected.

What it is: GHSA-27f5-xjrr-q9ff is a vulnerability in @opensearch-project/opensearch, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-27f5-xjrr-q9ff in the wild and no public exploit code.

Affected packages and fixed versions:
- @opensearch-project/opensearch (npm): affected all versions; no fix listed
- @opensearch-project/opensearch (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-27f5-xjrr-q9ff/ (Markdown: https://insights.sbomify.com/GHSA-27f5-xjrr-q9ff/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-27f5-xjrr-q9ff

---
From sbomify Insights: https://insights.sbomify.com/GHSA-27f5-xjrr-q9ff/
Summaries are generated and may contain mistakes; the official description above is the record.