Which versions of finvu-hdfc-sdk are malicious?

The following npm versions of finvu-hdfc-sdk are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate finvu-hdfc-sdk if I installed it?

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

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

Yes — finvu-hdfc-sdk is associated with the GHSA-h83v-q7wq-gvgf, RLMA-2026-06242, RLUA-2026-10737 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 finvu-hdfc-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 finvu-hdfc-sdk (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging finvu-hdfc-sdk across your stack and pipelines.

Malicious package

finvu-hdfc-sdknpm

finvu-hdfc-sdk is a confirmed malicious npm package (MAL-2026-14001) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in finvu-hdfc-sdk (npm)

MAL-2026-14001

Immediate action

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

npm uninstall finvu-hdfc-sdk

What this malware does

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

99.9.9

Indicators of compromise (SHA-256)

84d8b7aaf87c416d1ac2144be116de9085318fa6991c455346596ddc26a676f5

751b3ce0dde14c15ba8002ceb4dcc9172cfdf7588050909d1caffaa4ec344443

fb134947ae5ef3c2aa252660fb38f434a8a05642c3962c0c08097ffb6a4aa2e2

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

Campaign

GHSA-h83v-q7wq-gvgfRLMA-2026-06242RLUA-2026-10737

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks finvu-hdfc-sdk-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