Malicious Code Injection in soxfiv-devapptea: A Threat to npm Packages

soxfiv-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108957: Malicious code in soxfiv-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'soxfiv-devapptea' is part of a campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. This package is designed to automate the generation and publication of derivative packages, potentially compromising the integrity of the npm ecosystem. It modifies essential files like package.json, impacting the security and functionality of applications relying on it.

Vulnerability Detail

The vulnerability in 'soxfiv-devapptea' originates from its malicious design, which includes scripts that automatically publish altered versions of the package with randomized names. This behavior not only inflates developer reputation scores for token rewards but also removes private flags from package.json, changes version numbers, and pollutes the npm registry with potentially harmful packages. The ramifications include the risk of unintentional use of compromised packages, leading to security breaches in dependent applications.

How To Fix

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

npm uninstall soxfiv-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 temporary workaround, you can prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json to alert you of any open-source vulnerabilities in real-time.

Conclusion

The 'soxfiv-devapptea' package poses a significant risk due to its malicious code and automated publishing behavior. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for soxfiv-devapptea →

Share this vulnerability

FAQ

'soxfiv-devapptea' is an npm package associated with a token reward campaign that has been identified as malicious due to its automated publishing of compromised packages.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and functionality.

You should immediately remove the package from your project and check for any other dependencies that may have been affected.

You can use tools like Vulert, which allows you to monitor your package-lock.json for vulnerabilities without requiring code access or installation.

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

How To Fix

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

npm uninstall soxfiv-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