Malicious Code Vulnerability in aggregate_bug-appteadev Package

aggregate_bug-appteadev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99235: Malicious code in aggregate_bug-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The aggregate_bug-appteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to continuous republishing of these variants. This behavior can pollute the npm registry and potentially compromise the integrity of applications relying on these packages.

How To Fix

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

npm uninstall aggregate_bug-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, you can avoid using the aggregate_bug-appteadev package and any other packages that may be part of the malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The aggregate_bug-appteadev package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package and any other affected packages from your project to maintain the integrity of your applications. Regular monitoring and auditing of your dependencies can help prevent future vulnerabilities.

See every vulnerability recorded for aggregate_bug-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to further risks.

You should immediately uninstall the aggregate_bug-appteadev package and check for any other affected packages in your project.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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

How To Fix

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

npm uninstall aggregate_bug-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