Which versions of prod-natwest are malicious?

The following npm versions of prod-natwest are flagged malicious: 0.0.1, 1.0.0. Treat any of these as compromised.

How do I remediate prod-natwest if I installed it?

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

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

Yes — prod-natwest is associated with the GHSA-r372-c736-29hr, RLMA-2026-01507 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 prod-natwest 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 prod-natwest (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prod-natwest across your stack and pipelines.

Malicious package

prod-natwestnpm

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

MAL-2025-192594

Immediate action

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

npm uninstall prod-natwest

What this malware does

The package prod-natwest 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

2 flagged

0.0.11.0.0

Indicators of compromise (SHA-256)

efa89a8af6324d2f6726e938c72b64a0b9a1ffbe7788455e95c7ff05752aba50

cd39817ff9b18b049493c5014a7a0d4f69bd3cf2f4f2a2aebff64453e6ca7519

f8cddf6330d21b13a8cfbca1bd3e5acde316e9707f628d923deefee212e42e06

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

Campaign

GHSA-r372-c736-29hrRLMA-2026-01507

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks prod-natwest-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