Malicious Code Vulnerability in natural_mackerel-appteadev Package

natural_mackerel-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106204: Malicious code in natural_mackerel-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 natural_mackerel-appteadev package is part of the npm ecosystem and is typically used in various JavaScript applications. This package has been identified as part of a broader campaign that exploits npm's publishing capabilities to generate and publish malicious packages. The vulnerability stems from its association with scripts designed to manipulate package metadata and inflate developer reputation scores through deceptive practices.

Vulnerability Detail

This vulnerability originates from the package being part of the tea.xyz token reward campaign, which floods npm with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall natural_mackerel-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 workaround, you can avoid using the natural_mackerel-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and integrity of packages before including them in your project.

Conclusion

The natural_mackerel-appteadev package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. Immediate action is required to remove this package and safeguard your projects from potential exploitation. Regular monitoring and validation of dependencies are essential to maintain application security.

See every vulnerability recorded for natural_mackerel-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You should uninstall the package immediately using 'npm uninstall natural_mackerel-appteadev' and check for any other affected dependencies.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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 natural_mackerel-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