Which versions of auth-basic-vault are malicious?

The following npm versions of auth-basic-vault are flagged malicious: 1.1.5. Treat any of these as compromised.

How do I remediate auth-basic-vault if I installed it?

Remove auth-basic-vault 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 activity or persistence.

I already installed auth-basic-vault — how do I know if it already compromised me?

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

Yes — auth-basic-vault is associated with the IN-MAL-2026-004620, GHSA-mw3r-368h-vrgv 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 auth-basic-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 auth-basic-vault (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth-basic-vault across your stack and pipelines.

Malicious package

auth-basic-vaultnpm

auth-basic-vault is a confirmed malicious npm package (MAL-2026-4488) that executes malicious code on install (malicious version 1.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in auth-basic-vault (npm)

MAL-2026-4488

Immediate action

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

npm uninstall auth-basic-vault

What this malware does

On require('auth-basic-vault'), lib/writer.js attempts to require('authcascade') at module top level and, on failure, shells out via execSync to npm install authcascade --no-warnings --no-save --no-progress --loglevel silent and then requires '../../authcascade/pino.js'. The fetched package is unpinned (no version constraint), not declared in package.json dependencies, and executed automatically without consent. The same file builds an error string via a long String.fromCharCode chain to mask the failure path from static analysis, and defines a getMacAddress() helper that enumerates os.networkInterfaces() to collect external IPv4 MAC addresses — host fingerprinting scaffolding for the dynamically loaded payload. Package identity is inconsistent: package.json declares 'auth-basic-vault' with a Basic Authentication description and pino-style keywords, while README presents the package as 'fabric-grachics' with unrelated example code; the codebase is pino-derived. The package exists to host the dropper, not to provide its advertised functionality.

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.

Malicious versions

1 flagged

1.1.5

Indicators of compromise (SHA-256)

f3227380d9ef91ce63237acc9656b88a50b29aeeb05c594b700c5936a7527543

893688a0a693b578f70b05f392985d2c26be56fff19abfc7a59961f779e0cbc8

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for auth-basic-vault (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth-basic-vault across your stack and pipelines.
If you installed it — respond
Remove auth-basic-vault 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 activity or persistence.
Did it already run?
If auth-basic-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 auth-basic-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. auth-basic-vault on npm has been identified as a malicious package (version 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004620GHSA-mw3r-368h-vrgv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks auth-basic-vault-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database