Malicious Code Detected in angunote Package - Security Alert

angunote Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14539: Malicious code in angunote (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The angunote package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility in various projects. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the angunote package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall angunote

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, consider removing the angunote package from your project until a secure version is released. You can do this by executing the command: npm uninstall angunote.

Conclusion

The discovery of malicious code in the angunote package poses a serious threat to applications that utilize it. Users must take immediate action to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for angunote →

Share this vulnerability

FAQ

The angunote package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using the angunote package can lead to unauthorized access and data breaches due to the malicious code embedded within it.

Currently, there is no specific patch mentioned, but users are advised to update the package to the latest version or remove it until a secure version is released.

If you have used angunote, it is crucial to uninstall the package immediately and monitor your application for any suspicious activity.

How To Fix

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

npm uninstall angunote

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