Malicious Code Vulnerability in experienced_giraffe-gooddev Package

experienced_giraffe-gooddev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102380: Malicious code in experienced_giraffe-gooddev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The experienced_giraffe-gooddev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm registry but has been compromised to include malicious code. It is primarily used by developers to manage dependencies and automate tasks, but its integrity has been severely undermined due to this vulnerability.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the experienced_giraffe-gooddev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which are often themed around Indonesian culture. The malicious code is designed to continuously republish these variants, thereby polluting the npm registry and inflating developer reputation scores for token rewards. The ramifications of this vulnerability include potential exposure of sensitive data, disruption of package management, and degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall experienced_giraffe-gooddev

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 experienced_giraffe-gooddev package from your project by executing the following command: npm uninstall experienced_giraffe-gooddev. This will prevent the execution of the malicious code until a secure version is available.

Conclusion

The experienced_giraffe-gooddev package has been identified as containing malicious code that compromises its integrity and poses significant risks to developers and the npm ecosystem. It is essential to take immediate action by updating or uninstalling the package to mitigate these risks.

See every vulnerability recorded for experienced_giraffe-gooddev →

Share this vulnerability

FAQ

It is an npm package that has been compromised with malicious code, originally intended for managing dependencies and automating tasks.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to data exposure and registry pollution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As a workaround, you can uninstall the experienced_giraffe-gooddev package to prevent the execution of the malicious code until a secure version is released.

Detailed information can be found in the vulnerability report and by checking the npm registry for updates on the experienced_giraffe-gooddev package.

How To Fix

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

npm uninstall experienced_giraffe-gooddev

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