Malicious Code Detected in ajaxnotes Package - Security Alert

ajaxnotes Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14221: Malicious code in ajaxnotes (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 ajaxnotes package is an npm library designed for creating and managing notes in a web application. It offers features such as note organization, tagging, and synchronization across devices. However, this package has been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the ajaxnotes package originates from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of user data. The issue is particularly concerning as it affects all versions of the package starting from version 0, making it critical for users to take immediate action.

How To Fix

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

npm uninstall ajaxnotes

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, users can avoid using the ajaxnotes package and instead implement a custom note management solution or utilize other well-reviewed and secure packages available on npm.

Conclusion

The ajaxnotes package has been identified to contain malicious code, posing serious security risks to users. It is crucial for developers to take immediate action by removing the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining secure software practices.

See every vulnerability recorded for ajaxnotes →

Share this vulnerability

FAQ

The ajaxnotes package is an npm library used for creating and managing notes in web applications.

The malicious code can lead to unauthorized access and data breaches, compromising user data and application security.

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

You should remove the ajaxnotes package and consider using a secure alternative. If a patched version is released, update to that version.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

How To Fix

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

npm uninstall ajaxnotes

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