Which versions of valuedex-sdk are malicious?

The following npm versions of valuedex-sdk are flagged malicious: 3.0.5. Treat any of these as compromised.

How do I remediate valuedex-sdk if I installed it?

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

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

Yes — valuedex-sdk is associated with the GHSA-x462-r8jr-ch8w 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 valuedex-sdk 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 valuedex-sdk (version 3.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging valuedex-sdk across your stack and pipelines.

Malicious package

valuedex-sdknpm

Malicious code in valuedex-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191446

Immediate action

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

npm uninstall valuedex-sdk

What this malware does

The package valuedex-sdk was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

3.0.5

Indicators of compromise (SHA-256)

1cb1fdfb5f1c6c79322c050eca36bbc3b60bd373a855fe4e225d260b1e4378fd

14bcd330b75ba074bb0ea2ba295bf74570677a718d844ef4f7e18fbd051594da

7604b9b49dff9ce4a66119dcd337c975d53e669752a1964d523b95bce8b96761

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

Campaign

GHSA-x462-r8jr-ch8w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks valuedex-sdk-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