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?

vaults-monitor-cron 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 vaults-monitor-cron — how do I know if it already compromised me?

If vaults-monitor-cron 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 vaults-monitor-cron part of a known attack campaign?

Yes — vaults-monitor-cron is associated with the IN-MAL-2026-006487, RLMA-2026-05640 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 vaults-monitor-cron 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 vaults-monitor-cron (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 vaults-monitor-cron across your stack and pipelines.

Malicious package

vaults-monitor-cronnpm

vaults-monitor-cron is a confirmed malicious npm package (MAL-2026-5784) 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 vaults-monitor-cron (npm)

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

18042d06d50d5657384146376bfd0f18841c526ab28936b4054a0d426ad2a77d

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 vaults-monitor-cron (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 vaults-monitor-cron across your stack and pipelines.
If you installed it — respond
vaults-monitor-cron 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 vaults-monitor-cron 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 vaults-monitor-cron 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. 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-006487RLMA-2026-05640

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vaults-monitor-cron-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