Which versions of secrets-manager-wrapper are malicious?

The following npm versions of secrets-manager-wrapper are flagged malicious: 50.50.50. Treat any of these as compromised.

How do I remediate secrets-manager-wrapper if I installed it?

secrets-manager-wrapper 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 secrets-manager-wrapper — how do I know if it already compromised me?

If secrets-manager-wrapper 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 secrets-manager-wrapper part of a known attack campaign?

Yes — secrets-manager-wrapper is associated with the GHSA-fmm2-56pg-g4g7 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 secrets-manager-wrapper 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 secrets-manager-wrapper (version 50.50.50). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging secrets-manager-wrapper across your stack and pipelines.

Malicious package

secrets-manager-wrappernpm

Malicious code in secrets-manager-wrapper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3195

Immediate action

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

npm uninstall secrets-manager-wrapper

What this malware does

Dependency confusion and typosquatting campaign by threat actor "saif777". Packages use inflated version numbers (9999.9999.9999, 9999.9999.10000, 50.50.50, 7.66.5) to win version resolution in environments with private registries. All active packages execute a postinstall hook ("node index.js") that collects a system fingerprint — public IP (via api.ipify.org), username, hostname, CPU model, RAM, working directory, OS platform — and exfiltrates it as a Discord embed to a shared webhook (base64-obfuscated in source). Payloads include sandbox/bot detection: machines with ≤1 CPU or <2 GB RAM are flagged as sandbox/CI; real machines trigger a green embed. Targets organisations with a private secrets-manager-wrapper package.

The package secrets-manager-wrapper 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.

The OpenSSF Package Analysis project identified 'secrets-manager-wrapper' @ 50.50.50 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

50.50.50

Indicators of compromise (SHA-256)

96381835a1a11855d6f9cfaa8aba6f1ec9c16219795064e1831aa396f45410ae

ec5d60dca99a10bcb9941d1d34e95d2134e55308aaf04f6aaa11d9135a398501

768199ced9521dff5d06dbf72616fe2fbec7e7fafa3ecb7783a4ad038e874f61

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 secrets-manager-wrapper (version 50.50.50). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging secrets-manager-wrapper across your stack and pipelines.
If you installed it — respond
secrets-manager-wrapper 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 secrets-manager-wrapper 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 secrets-manager-wrapper 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. secrets-manager-wrapper on npm has been identified as a malicious package (version 50.50.50 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fmm2-56pg-g4g7

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks secrets-manager-wrapper-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