Malicious Code Injection in wdgisf-devapp: npm Package Vulnerability

wdgisf-devapp Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110762: Malicious code in wdgisf-devapp (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 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

wdgisf-devapp is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the development of applications using the tea protocol. However, this package has been identified as containing malicious code that can compromise the integrity of the npm registry and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in wdgisf-devapp originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall wdgisf-devapp

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

As a temporary workaround, you can remove the wdgisf-devapp package from your project to prevent any potential exploitation. Use the following command to uninstall the package: 'npm uninstall wdgisf-devapp'.

Conclusion

The wdgisf-devapp package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your applications.

See every vulnerability recorded for wdgisf-devapp →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

Using this package can lead to security breaches, as it may introduce malicious code into your application and compromise the integrity of the npm registry.

Check the npm repository for wdgisf-devapp to see if a patched version is available and update accordingly.

Uninstall the package immediately and check your application for any potential security issues that may have arisen from its use.

How To Fix

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

npm uninstall wdgisf-devapp

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