Malicious Code Injection in aylessa-notthedevs: A Threat to npm Packages

aylessa-notthedevs Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99726: Malicious code in aylessa-notthedevs (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 package 'aylessa-notthedevs' 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 aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in 'aylessa-notthedevs' originates from its malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only clutters the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall aylessa-notthedevs

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 'aylessa-notthedevs' package until a patched version is released. Additionally, consider using tools like Vulert to monitor your application for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The aylessa-notthedevs package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for aylessa-notthedevs →

Share this vulnerability

FAQ

The aylessa-notthedevs package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the installation of malicious packages that may compromise your application's integrity and security, potentially allowing unauthorized access or data manipulation.

If you have installed the aylessa-notthedevs package, it is recommended to remove it immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. Visit https://vulert.com for more information.

To prevent similar vulnerabilities, regularly update your dependencies, use trusted sources for packages, and employ security monitoring tools like Vulert to stay informed about potential risks.

How To Fix

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

npm uninstall aylessa-notthedevs

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