Which versions of @cap-js/openapi are malicious?

The following npm versions of @cap-js/openapi are flagged malicious: 1.4.1. Treat any of these as compromised.

How do I remediate @cap-js/openapi if I installed it?

@cap-js/openapi 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 @cap-js/openapi — how do I know if it already compromised me?

If @cap-js/openapi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @cap-js/openapi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @cap-js/openapi (version 1.4.1).

Malicious package

@cap-js/openapinpm

Advisory published May 19, 2026Updated May 19, 2026

@cap-js/openapi is a confirmed malicious npm package (MAL-2026-4161) that steals credentials and exfiltrates sensitive data (malicious version 1.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @cap-js/openapi (npm)

MAL-2026-4161

Immediate action

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

npm uninstall @cap-js/openapi

What this malware does

The package @cap-js/openapi was found to contain malicious code.

This package was compromised as part of the ongoing "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

1 flagged

1.4.1

Indicators of compromise (SHA-256)

847ef6b381d410bf176f7414a6f0fbbcf46a5f39b6d9011e126b279bd2d781df

243c059793e8b277fc77959046b7b064cb740d568fa53e4d30b9075660d9dab5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @cap-js/openapi (version 1.4.1).
If you installed it — respond
@cap-js/openapi 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 @cap-js/openapi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @cap-js/openapi on npm has been identified as a malicious package (version 1.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @cap-js/openapi-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

Explore

All malware advisories How O3 detects malware Vulnerability database