Malicious Code Vulnerability in okay_goose-tool Package

okay_goose-tool Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106619: Malicious code in okay_goose-tool (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The okay_goose-tool package is part of the npm ecosystem and is designed for various utility functions. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms. This package is involved in generating and publishing derivative packages with the intent to inflate developer reputation scores for token rewards, making it a target for malicious actors.

Vulnerability Detail

The vulnerability in the okay_goose-tool package stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially 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 okay_goose-tool

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 workaround, you can avoid using the okay_goose-tool package entirely and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

Conclusion

The okay_goose-tool package has been identified as having a serious vulnerability due to its association with a malicious campaign. It is crucial for developers to remove this package and monitor their applications for any potential security threats. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for okay_goose-tool →

Share this vulnerability

FAQ

The okay_goose-tool package is an npm package designed for utility functions but has been identified as part of a malicious campaign.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should remove the package from your project immediately and monitor for any signs of compromise.

You can use tools like Vulert, which monitors your package-lock.json file and alerts you in real-time for any open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall okay_goose-tool

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