Malicious Code Injection in jolly_sole_purple-65: A Threat to npm Packages

jolly_sole_purple-65 Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104667: Malicious code in jolly_sole_purple-65 (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

jolly_sole_purple-65 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is designed to exploit the npm registry by generating and publishing derivative packages with randomized names. Its primary function appears to be to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The package's malicious behavior includes modifying critical files and continuously republishing variants to pollute the npm registry.

Vulnerability Detail

The vulnerability in jolly_sole_purple-65 stems from its malicious code, which is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages. The origin of this vulnerability is linked to a broader campaign that floods the npm ecosystem with harmful packages, making it essential for developers to remain vigilant.

How To Fix

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

npm uninstall jolly_sole_purple-65

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 measure, you can avoid using the jolly_sole_purple-65 package and any other packages that may have been published as part of this malicious campaign. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The jolly_sole_purple-65 package poses a significant threat to the npm ecosystem due to its malicious code that alters package files and publishes harmful variants. It is essential for developers to be proactive in removing this package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for jolly_sole_purple-65 →

Share this vulnerability

FAQ

jolly_sole_purple-65 is an npm package identified as part of a malicious campaign that modifies package files and publishes harmful variants.

The vulnerability can compromise your project's integrity by introducing malicious code and potentially exposing your application to further attacks.

You should uninstall the jolly_sole_purple-65 package immediately using the command: npm uninstall jolly_sole_purple-65.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time 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 signing up.

How To Fix

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

npm uninstall jolly_sole_purple-65

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