Critical Malicious Code Vulnerability in prod-natwest Package

prod-natwest Updated 16 Dec 2025

Summary

16/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192594: Malicious code in prod-natwest (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The prod-natwest package is an npm library designed for specific functionalities within Node.js applications. It is utilized by developers to streamline certain processes. However, this package has been identified as containing malicious code, which poses significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the prod-natwest package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full control of the affected system by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall prod-natwest

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure to monitor your systems for any unusual activity following the removal.

Conclusion

The prod-natwest package has been identified as containing malicious code that compromises systems upon installation. Immediate removal of the package and rotation of sensitive information is essential to mitigate risks. Users should remain vigilant and consider using tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for prod-natwest →

Share this vulnerability

FAQ

The prod-natwest package is an npm library used in Node.js applications, but it has been found to contain malicious code.

If you have the prod-natwest package installed, your system is considered compromised. It is recommended to remove it immediately.

After removal, rotate all secrets and keys stored on the affected machine from a secure system to prevent unauthorized access.

No, there is currently no patch available for the prod-natwest package. The only solution is to remove it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall prod-natwest

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback