Malicious Code Injection in giddol-devapptea: A Threat to npm Ecosystem

giddol-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103122: Malicious code in giddol-devapptea (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

giddol-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing scripts. However, it has been identified as containing malicious code that compromises the integrity of the npm ecosystem by generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the giddol-devapptea package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the pollution of the npm registry, potentially affecting developers' reputation scores and the overall trustworthiness of the ecosystem. The malicious payload can also lead to unintended consequences for applications relying on this package.

How To Fix

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

npm uninstall giddol-devapptea

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 measure, avoid using the giddol-devapptea package and consider using alternative packages that do not exhibit malicious behavior. Regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The giddol-devapptea package poses a significant risk to the npm ecosystem due to its malicious code that alters package metadata and publishes unauthorized variants. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for giddol-devapptea →

Share this vulnerability

FAQ

giddol-devapptea is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and compromising your project's integrity.

You should uninstall the package immediately using the command npm uninstall giddol-devapptea to mitigate any risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall giddol-devapptea

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