Malicious Code Injection in jacobthomas Package: npm Vulnerability Overview
Summary
MAL-2025-171394: Malicious code in jacobthomas (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The jacobthomas package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The package's functionality is compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability originates from the jacobthomas package being associated with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry. This can have serious ramifications, including the potential for developers to unknowingly install compromised packages, leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jacobthomasIf 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 avoid using the jacobthomas package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The jacobthomas package poses a significant security risk due to its association with a malicious campaign aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, uninstall any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for jacobthomas →
FAQ
The jacobthomas package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.
You should uninstall the jacobthomas package immediately using the command 'npm uninstall jacobthomas' and check for any other affected packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against the Vulert playground without any signup.
Yes, you should look for alternative packages that offer similar functionality but are verified and do not have known vulnerabilities.
