Malicious Code Injection in surya-nasipecel12-breki Package

surya-nasipecel12-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75538: Malicious code in surya-nasipecel12-breki (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 surya-nasipecel12-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publishing of derivative packages. This package, like others in its category, aims to inflate developer reputation scores for token rewards, making it a target for malicious activities.

Vulnerability Detail

The vulnerability in the surya-nasipecel12-breki package stems from its inclusion in a malicious campaign that employs autopublish scripts. These scripts 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 malicious payload can significantly impact developers by compromising their package integrity and reputation.

How To Fix

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

npm uninstall surya-nasipecel12-breki

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 surya-nasipecel12-breki package from your project by executing: npm uninstall surya-nasipecel12-breki. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The surya-nasipecel12-breki package contains a serious vulnerability that can compromise the integrity of projects using it. It is crucial to take immediate action by updating or removing the package and monitoring your project for vulnerabilities using tools like Vulert.

See every vulnerability recorded for surya-nasipecel12-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed for automatic package generation and publishing.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and reputation.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall surya-nasipecel12-breki

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