Malicious Code Injection in seblakkuah21: A Threat to npm Ecosystem

seblakkuah21 Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108458: Malicious code in seblakkuah21 (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 package seblakkuah21 is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in seblakkuah21 involves malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry and inflate developer reputation scores for token rewards. The malicious payload can lead to the proliferation of untrustworthy packages, potentially compromising the integrity of applications that depend on them.

How To Fix

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

npm uninstall seblakkuah21

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 seblakkuah21 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any changes using tools like Vulert.

Conclusion

The seblakkuah21 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and proliferates untrustworthy packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application integrity.

See every vulnerability recorded for seblakkuah21 →

Share this vulnerability

FAQ

Seblakkuah21 is an npm package that has been identified as malicious, involved in a scheme to manipulate developer reputation scores.

The malicious code can alter your package.json file, leading to the proliferation of untrustworthy packages and potentially compromising your application's integrity.

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

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, 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 seblakkuah21

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