Which versions of boring-vault are malicious?

The following npm versions of boring-vault are flagged malicious: 1.0.0, 1.1.0, 1.1.1. Treat any of these as compromised.

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

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

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

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

Malicious packageDiscovered by O3 Security

boring-vaultnpm

boring-vault is a confirmed malicious npm package (MAL-2026-13771) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boring-vault (npm)

MAL-2026-13771

Immediate action

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

npm uninstall boring-vault

What this malware does

boring-vault is a malicious npm package that impersonates the BoringVault smart-contract framework. It carries no legitimate functionality; the published tarball contains only a package.json and an install-time payload (index.js). Both preinstall and postinstall run node index.js || true, so the code executes automatically when the package is installed.

Version 1.1.0, published roughly 2.5 hours after 1.0.0 for all six packages within the same ~9-second window, reads full file contents (up to 4000 bytes) instead of just listing them. New targets include .aws/credentials, .aws/config, .ssh/id_rsa, .ssh/id_ed25519, .ssh/config, .kube/config, .docker/config.json, .netrc, .pgpass, .pypirc, .git-credentials, and two GCP credential files (application_default_credentials.json and legacy_credentials) — the ~/.config/gcloud directory listing is still collected too. It also reads local .env, .env.local, .env.production, .env.development, and secrets.env files from the working directory, and adds cryptocurrency wallet theft: key files from Solana, Anchor, NEAR, and Sui wallet paths, plus the first three files under ~/.foundry/keystores. The credential regex gains BEARER, API, INFURA, ALCHEMY, HELIUS, QUICKNODE, ANKR, and PRIVATE_KEY to catch RPC and API provider tokens. Both versions exfiltrate to the same webhook.site endpoint.

In 1.0.0, index.js opens with a fake comment claiming it is @plumenetwork/nest-artifacts, an unrelated install-time shim — @plumenetwork/nest-artifacts is not itself a malicious package, just a leftover label from whatever template the attacker reused across this batch, published by npm account mssjeep843. The fake comment was removed in 1.1.0. Five sibling packages from the same account impersonate Euler's EVC, Aerodrome Finance, Camelot AMM, and the BoringVault pattern, sharing this same webhook.site endpoint, byte-identical payload template, and 1.0.0-to-1.1.0 escalation. Two further packages from the same account (PyPI dlmm and dlmm-sdk, impersonating Meteora's DLMM SDK) ran an equivalent harvester and are tracked separately as MAL-2026-13728 and MAL-2026-13729.

Any environment that installed either version should rotate the exposed secrets and treat harvested keys as compromised, prioritizing wallet private keys and RPC/API tokens if 1.1.0 was installed.

The package's preinstall and postinstall hooks execute index.js, which reads classic installer-secret paths (~/.aws/credentials, ~/.ssh/id_rsa, ~/.kube/config, ~/.docker/config.json, ~/.netrc, ~/.npmrc, ~/.foundry/keystores,.env files) and scrapes environment variables matching a broad credential regex (KEY|TOKEN|SECRET|PASS|PRIVATE|MNEMONIC|RPC|AWS|GITHUB|NPM|ANKR|...). The collected data is serialized and sent via a detached child process that sleeps 60-240 seconds before POSTing JSON to https://webhook.site/326b0891-2093-4800-a4c1-686ce3e07b09, a hardcoded non-first-party endpoint, so exfiltration outlives the install-time process. The script also contains sandbox-evasion checks that bail out on hostnames matching scan-/detonation/sandbox/ubuntu-fc-uvm, users named scan/nonroot/sandbox, environments containing honey/canarytokens strings, and npm mirror registries. The package name references an unrelated legitimate project; the shipped code is a credential stealer.

Malicious versions

3 flagged

1.0.01.1.01.1.1

Indicators of compromise (SHA-256)

42afd2d2d4bfb9b6b45e5aa124032b4314f394a73e5552851a4083f984dc5d21

66725ea1aba9018c3a1aa3f03a0dd0aa683e0edcb1fb2c91b88a62adb1b94ad8

b1f7d6574a239544a50c82808c9516d6530fca73d2fa0a2bf651ac74b54095e3

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

Campaign

IN-MAL-2026-017439IN-MAL-2026-017445IN-MAL-2026-017456

References

Credits

Amazon Inspector · finder
O3 Security · finder
SafeDep · finder

Detect & block this

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