Malicious Code Injection in objective_grouse_requirement Package

objective_grouse_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95709: Malicious code in objective_grouse_requirement (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 objective_grouse_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the integration of various functionalities within a project. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability stems from the package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This can lead to developers inadvertently using compromised packages, exposing their applications to potential security threats.

How To Fix

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

npm uninstall objective_grouse_requirement

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 avoid using the objective_grouse_requirement package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before integrating them into your project.

Conclusion

The objective_grouse_requirement package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is essential to remove this package and monitor your dependencies for vulnerabilities to ensure the security of your projects.

See every vulnerability recorded for objective_grouse_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.

The malicious code modifies your package.json file, potentially exposing your application to security vulnerabilities and compromising its integrity.

You should uninstall the package immediately using 'npm uninstall objective_grouse_requirement' and check your project for any other compromised dependencies.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Yes, you should look for alternative packages that provide similar functionality but have a good reputation and are actively maintained.

How To Fix

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

npm uninstall objective_grouse_requirement

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