Malicious Code Injection in wawan-nasipecel28-sluey Package

wawan-nasipecel28-sluey Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92142: Malicious code in wawan-nasipecel28-sluey (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The wawan-nasipecel28-sluey 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 publishing of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is primarily centered around package management and publishing in the npm registry.

Vulnerability Detail

The vulnerability in the wawan-nasipecel28-sluey package stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem, allowing for potential exploitation and misuse of developer reputation systems.

How To Fix

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

npm uninstall wawan-nasipecel28-sluey

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 wawan-nasipecel28-sluey package from your project by executing: npm uninstall wawan-nasipecel28-sluey. This will prevent any malicious code from executing until a fix is available.

Conclusion

The wawan-nasipecel28-sluey package contains a significant vulnerability that allows for malicious code injection, potentially compromising the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to protect their projects.

See every vulnerability recorded for wawan-nasipecel28-sluey →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publishing of packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should update the package to a patched version or remove it from your project to mitigate the risk.

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

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 wawan-nasipecel28-sluey

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