Malicious Code Vulnerability in graceroberts Package

graceroberts Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171274: Malicious code in graceroberts (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 graceroberts package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability in the graceroberts package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This activity not only pollutes the npm registry but also modifies the package.json file to remove private flags and change version numbers. The malicious payload can lead to significant security risks, including unauthorized access to sensitive information and the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall graceroberts

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 graceroberts package from your project by executing the following command: npm uninstall graceroberts. This will prevent any malicious code from executing while you assess your options for replacing the package.

Conclusion

The graceroberts package has been identified as containing malicious code that poses significant security risks. It is crucial for developers to take immediate action by updating or removing the package to protect their applications from potential exploitation. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for graceroberts →

Share this vulnerability

FAQ

The graceroberts package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to unauthorized modifications of your package.json file and the potential for malicious code execution, which can compromise your application's security.

You should immediately update the package to the latest version or remove it from your project to mitigate the risks associated with this vulnerability.

Yes, you can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Vulert is a service that allows you to monitor open-source vulnerabilities using just your package-lock.json file, providing real-time alerts for any issues that may arise.

How To Fix

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

npm uninstall graceroberts

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