Malicious Code Injection in galangwijaya: A Threat to npm Users

galangwijaya Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171245: Malicious code in galangwijaya (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 'galangwijaya' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of 'galangwijaya' is to serve as a token reward mechanism for the tea.xyz protocol, which has been compromised to inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'galangwijaya' package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names, predominantly themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall galangwijaya

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 'galangwijaya' package and any other packages that may be part of the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'galangwijaya' package poses a significant threat due to its malicious code designed to exploit the npm registry. Users are advised to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is crucial in maintaining the security of your software.

See every vulnerability recorded for galangwijaya →

Share this vulnerability

FAQ

The 'galangwijaya' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign, which has been compromised to exploit the npm registry.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.

You should uninstall the 'galangwijaya' package immediately using 'npm uninstall galangwijaya' and monitor your project for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can check your application at the Vulert playground without needing to sign up.

Currently, there is no patched version available for 'galangwijaya'. It is recommended to remove the package entirely until a secure version is released.

How To Fix

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

npm uninstall galangwijaya

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