Malicious Code Injection in kerry-soluble-pot: A Threat to npm Users

kerry-soluble-pot Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104762: Malicious code in kerry-soluble-pot (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

kerry-soluble-pot is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the same campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. It modifies essential files, including package.json, to facilitate its malicious activities.

Vulnerability Detail

The vulnerability in kerry-soluble-pot arises from its inclusion in a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also compromises the integrity of the package by altering critical metadata, such as removing private flags and changing version numbers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes developers to publish more packages, leading to potential exploitation and misuse.

How To Fix

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

npm uninstall kerry-soluble-pot

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 kerry-soluble-pot package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages to identify and remove any potentially malicious packages.

Conclusion

The kerry-soluble-pot package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.

See every vulnerability recorded for kerry-soluble-pot →

Share this vulnerability

FAQ

kerry-soluble-pot is an npm package identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, compromise the integrity of your project, and potentially expose your application to security risks.

You should uninstall the kerry-soluble-pot package immediately using the command npm uninstall kerry-soluble-pot and audit your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor your package-lock.json file for vulnerabilities and provide alerts in real-time.

How To Fix

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

npm uninstall kerry-soluble-pot

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