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

mercer-soluble-pot Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105799: Malicious code in mercer-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

The package 'mercer-soluble-pot' is part of a larger ecosystem of npm packages that have been identified as malicious. These packages are often linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publishing of derivative packages. The malicious nature of this package lies in its ability to modify important files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'mercer-soluble-pot' originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, which can lead to a cluttered npm registry and potential security risks for developers relying on these packages. The malicious payload is specifically crafted to exploit the npm ecosystem, making it a significant threat.

How To Fix

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

npm uninstall mercer-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 workaround, you can remove the 'mercer-soluble-pot' package from your project by executing: 'npm uninstall mercer-soluble-pot'. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The 'mercer-soluble-pot' package poses a significant threat due to its malicious code designed to manipulate npm's package registry. It is essential for developers to remain vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential risks.

See every vulnerability recorded for mercer-soluble-pot →

Share this vulnerability

FAQ

'mercer-soluble-pot' is an npm package that has been identified as malicious, part of a campaign to manipulate npm's package registry.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.

If you have installed 'mercer-soluble-pot', it is crucial to uninstall it immediately and check for any unauthorized changes in your project.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by simply analyzing your package-lock.json file.

Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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