Which versions of @opensearch-project/opensearch are malicious?

The following npm versions of @opensearch-project/opensearch are flagged malicious: 3.5.3, 3.6.2, 3.7.0, 3.8.0. Treat any of these as compromised.

How do I remediate @opensearch-project/opensearch if I installed it?

@opensearch-project/opensearch is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @opensearch-project/opensearch — how do I know if it already compromised me?

If @opensearch-project/opensearch was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @opensearch-project/opensearch part of a known attack campaign?

Yes — @opensearch-project/opensearch is associated with the GHSA-298w-vvm4-ww55 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @opensearch-project/opensearch across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @opensearch-project/opensearch (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @opensearch-project/opensearch across your stack and pipelines.

Malicious package

@opensearch-project/opensearchnpm

Malicious code in @opensearch-project/opensearch (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3434

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @opensearch-project/opensearch

What this malware does

The package @opensearch-project/opensearch was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, 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.

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

4 flagged

3.5.33.6.23.7.03.8.0

Indicators of compromise (SHA-256)

bc9446e1580e90011f7691e3f05331e3df74d06312cebfd3f413f996ac9e5a55

6c22989c0db8d85970948ed448b645259f408e6f3205b3acbea2138fffbacecc

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

1668370f4091d14b4e74ad0e9b25c70ccbc5bf7fb7d97f535212ce2289e71347

ab64dbef9fced7877f19cb2c597927dfc6f72eb04489024bbe4a2cc073a97b2c

a242bd81093992828073878d9bf4034a658d688f31ed7d25d0450f9b84d1cc51

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @opensearch-project/opensearch (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @opensearch-project/opensearch across your stack and pipelines.
If you installed it — respond
@opensearch-project/opensearch is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @opensearch-project/opensearch was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @opensearch-project/opensearch before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @opensearch-project/opensearch on npm has been identified as a malicious package (versions 3.5.3, 3.6.2, 3.7.0, 3.8.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-298w-vvm4-ww55

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @opensearch-project/opensearch-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring