Which versions of nodenetbanxsdk are malicious?

The following npm versions of nodenetbanxsdk are flagged malicious: 25.6.7. Treat any of these as compromised.

How do I remediate nodenetbanxsdk if I installed it?

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

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

Yes — nodenetbanxsdk is associated with the GHSA-549w-jx4q-46gw, RLMA-2025-06435, RLUA-2026-01462 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 nodenetbanxsdk 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 nodenetbanxsdk (version 25.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodenetbanxsdk across your stack and pipelines.

Malicious package

nodenetbanxsdknpm

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

MAL-2025-191542

Immediate action

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

npm uninstall nodenetbanxsdk

What this malware does

The package nodenetbanxsdk 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.

Malicious versions

1 flagged

25.6.7

Indicators of compromise (SHA-256)

d369a1b27a2dd8b6f16340c943462366dc30c2e54cf93cc4697c498c646d061d

d713c278d17ee8b13193f95b612afbe466e885e58f6cab96ccc1ce764b9d7e27

91aa320b8ca1764cba86e8368e4d1af01ccf9887567555869c3134379e4dc5e7

89c08cd99286511515cf01a85cae8f815f81d124036a5268086d1a3b31a08642

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

Campaign

GHSA-549w-jx4q-46gwRLMA-2025-06435RLUA-2026-01462

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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