Critical Malicious Code Vulnerability in @pradhumngautam/common-app Package

@pradhumngautam/common-app Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191048: Malicious code in @pradhumngautam/common-app (npm). Affects @pradhumngautam/common-app versions 1.0.2. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @pradhumngautam/common-app package is a Node.js library available via npm, designed for common application functionalities. It is widely used in various projects for its utility features. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the package containing embedded malicious code, which can compromise the entire system where it is installed. This malicious code can lead to unauthorized access, data breaches, and potential control over the affected system. Users are advised to treat any system with this package installed as fully compromised, necessitating immediate action to secure sensitive information.

How To Fix

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

npm uninstall @pradhumngautam/common-app

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

There are no effective workarounds for this vulnerability other than removing the package entirely. It is essential to monitor your system for any signs of compromise after the package has been uninstalled.

Conclusion

The @pradhumngautam/common-app package contains malicious code that poses a serious threat to any system using it. Immediate uninstallation and security measures are required to mitigate risks. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for @pradhumngautam/common-app →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Leaving this package installed can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

No patched version is available. The only solution is to uninstall the package completely.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and keep your packages updated.

How To Fix

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

npm uninstall @pradhumngautam/common-app

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