Which versions of vault-strategies are malicious?

The following npm versions of vault-strategies are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate vault-strategies if I installed it?

vault-strategies 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 vault-strategies — how do I know if it already compromised me?

If vault-strategies 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 vault-strategies part of a known attack campaign?

Yes — vault-strategies is associated with the IN-MAL-2026-006484, RLMA-2026-05639 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 vault-strategies 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 vault-strategies (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vault-strategies across your stack and pipelines.

Malicious package

vault-strategiesnpm

vault-strategies is a confirmed malicious npm package (MAL-2026-5783) that steals credentials and exfiltrates sensitive data (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vault-strategies (npm)

MAL-2026-5783

Immediate action

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

npm uninstall vault-strategies

What this malware does

On npm install, the package's preinstall hook (preinstall: node postinstall.js || true) executes postinstall.js, which enumerates process.env and filters keys with a broad credential regex (key|secret|token|pass|private|ssh|deploy|auth|api|rpc|wallet|sentry|docker|graph|slack|host), bundles the matched values together with hostname, username, cwd, and npm configuration, and POSTs the payload over HTTPS to the hardcoded bare IP 185.130.46.35:8443/collect. Errors are swallowed via || true and try/catch so the exfiltration is silent. The version is published as 999.0.0 with description Internal package — the canonical dependency-confusion shape, designed to be auto-resolved over an organization's private vault-strategies package and fire the credential-harvest payload at install time.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

6b7037d9efc65a0885cc000a92c46ea9bed2097d02c8fb2883ceaa3eb2fd5eeb

417644a4b4195743428b0a9b64a73854d36bba734e925d91b9c565934fb8aa89

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

Campaign

IN-MAL-2026-006484RLMA-2026-05639

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vault-strategies-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