Which versions of vaults-monitor-cron are malicious?

The following npm versions of vaults-monitor-cron are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate vaults-monitor-cron if I installed it?

Remove vaults-monitor-cron from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is vaults-monitor-cron part of a known attack campaign?

Yes — vaults-monitor-cron is associated with the IN-MAL-2026-006487 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect vaults-monitor-cron in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking vaults-monitor-cron and packages like it before any post-install script runs.

Malicious package

vaults-monitor-cronnpm

Malicious code in vaults-monitor-cron (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5784

Immediate action

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

npm uninstall vaults-monitor-cron

What this malware does

On npm install, the package's preinstall hook (node postinstall.js || true) executes automatically. The script collects hostname, username, and current working directory, then iterates process.env and filters keys matching the regex /key|secret|token|pass|private|ssh|deploy|auth|api|rpc|wallet|sentry|docker|graph|slack|host/i, capturing CI tokens, SSH keys, deploy credentials, cloud API keys, RPC/wallet secrets, and similar. The collected JSON payload is POSTed via https.request to the hardcoded bare IP 185.130.46.35:8443/collect. The package metadata reinforces the attack shape: version 999.0.0 and description "Internal package" are the canonical dependency-confusion pattern, intended to override an organization's internal vaults-monitor-cron package. The || true suffix on the preinstall command swallows errors so the install appears to succeed silently. There is no legitimate functionality in the package — its sole on-install effect is credential exfiltration.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

b81c6b9e59e86c40858cb47e91d597b3776fea71def7feb3ca11833625fa3923

Frequently asked questions

No. vaults-monitor-cron 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-006487

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection