Malicious Code Injection in great_bass-appteadev: npm Package Vulnerability

great_bass-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103368: Malicious code in great_bass-appteadev (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 great_bass-appteadev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to facilitate development processes, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the great_bass-appteadev package, which contains malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names to inflate developer reputation scores. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers relying on this package.

How To Fix

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

npm uninstall great_bass-appteadev

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 measure, avoid using the great_bass-appteadev package until a secure version is released. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The great_bass-appteadev package has been identified as containing malicious code that poses significant risks to developers. Immediate action is required to remove the package and monitor for updates. Utilizing tools like Vulert can help maintain the security of your projects by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for great_bass-appteadev →

Share this vulnerability

FAQ

It is an npm package used in JavaScript development, but it has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately and monitor for any updates or patches.

You can use Vulert, which allows you to check your package-lock.json for vulnerabilities without requiring code access or installation.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall great_bass-appteadev

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