Malicious Code Injection in svqkuj-devapptea: npm Package Vulnerability

svqkuj-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109414: Malicious code in svqkuj-devapptea (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The svqkuj-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through automated publishing of derivative packages. The functionality of svqkuj-devapptea is compromised due to its malicious intent, which includes altering package metadata and continuously republishing variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package svqkuj-devapptea, which contains malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and repackages them to inflate the developer's reputation. This behavior can lead to significant security risks, including the potential for dependency confusion and the introduction of further vulnerabilities into applications that rely on this package.

How To Fix

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

npm uninstall svqkuj-devapptea

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 workaround, you can manually remove the svqkuj-devapptea package from your project by running the command: npm uninstall svqkuj-devapptea. Additionally, consider using tools like Vulert to monitor your package-lock.json file for any vulnerabilities in real-time.

Conclusion

The svqkuj-devapptea package poses a significant security risk due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your project and monitor for any other vulnerabilities using tools like Vulert.

See every vulnerability recorded for svqkuj-devapptea →

Share this vulnerability

FAQ

svqkuj-devapptea is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and dependency confusion in your application.

You should uninstall the svqkuj-devapptea package immediately and monitor your project for any other potentially malicious packages.

You can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring access to the code or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall svqkuj-devapptea

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