Malicious Code Vulnerability in gilang-tempe50-remi Package

gilang-tempe50-remi Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103168: Malicious code in gilang-tempe50-remi (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gilang-tempe50-remi package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability in the gilang-tempe50-remi package originates from its inclusion in a campaign that floods npm with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers using this package, as it can lead to unauthorized access and misuse of their projects.

How To Fix

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

npm uninstall gilang-tempe50-remi

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 gilang-tempe50-remi package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The gilang-tempe50-remi package contains a significant vulnerability due to its malicious code, which can compromise the integrity of projects that utilize it. It is crucial to remove this package and monitor your dependencies for any similar threats. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for gilang-tempe50-remi →

Share this vulnerability

FAQ

The gilang-tempe50-remi package is an npm package associated with a token reward campaign that generates and publishes derivative packages.

The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially compromising its security and integrity.

If you have installed the gilang-tempe50-remi package, you should uninstall it immediately using npm uninstall gilang-tempe50-remi.

Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access.

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

How To Fix

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

npm uninstall gilang-tempe50-remi

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