npm package report

Is @medusajs/medusa-oas-cli safe?

Versions 2.11.4-preview-20251124090208, 2.11.4-preview-20251124032825 and 2.11.4-preview-20251124060135 of @medusajs/medusa-oas-cli were compromised. Other versions are not flagged as malicious.

Do not install @medusajs/medusa-oas-cli 2.11.4-preview-20251124090208, 2.11.4-preview-20251124032825 or 2.11.4-preview-20251124060135

CRITICAL

Compromised releases. Added to CyberXYZ 2025-11-24, OSV malicious-package feed (Google / OpenSSF).

// what we observed

The package @medusajs/medusa-oas-cli 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.

Reported by Amazon Inspector and GitHub Advisory Database via OSV.

// versions and what to do

Malicious: 2.11.4-preview-20251124090208, 2.11.4-preview-20251124032825, 2.11.4-preview-20251124060135
Move to: 2.22.2 newest 2.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @medusajs/medusa-oas-cli@2.22.2

OSV record advisory

// reach

0 direct dependencies

none carry a known advisory

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-10-31 at 00:01 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.