Malicious Code Injection in key_mastodon-toolteadev Package

key_mastodon-toolteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104766: Malicious code in key_mastodon-toolteadev (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 key_mastodon-toolteadev package is part of the npm ecosystem and is utilized in various applications for its functionalities related to the Mastodon social network. However, this package has been compromised, leading to significant security concerns. It is designed to facilitate interactions with the Mastodon API but has been exploited to include malicious scripts that can harm users and developers alike.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the key_mastodon-toolteadev package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names to inflate developer reputation scores. The malicious code is part of a broader campaign that floods the npm registry with derivative packages, potentially leading to reputational damage for developers and security risks for users. The continuous republishing of these variants pollutes the npm registry, making it difficult to identify legitimate packages.

How To Fix

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

npm uninstall key_mastodon-toolteadev

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 key_mastodon-toolteadev package from your project until a safe version is confirmed. Use the following command to uninstall the package: npm uninstall key_mastodon-toolteadev. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The key_mastodon-toolteadev package has been identified as containing malicious code that poses significant risks to developers and users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for key_mastodon-toolteadev →

Share this vulnerability

FAQ

It is an npm package used for interacting with the Mastodon social network, but it has been compromised with malicious code.

The malicious code can modify your package.json file, remove private flags, and flood the npm registry with harmful packages, potentially leading to security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As a workaround, consider uninstalling the key_mastodon-toolteadev package until a safe version is available.

Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall key_mastodon-toolteadev

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