Critical Malicious Code Vulnerability in asatoafm Package

asatoafm Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14886: Malicious code in asatoafm (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 asatoafm package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and functionality. However, it has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the asatoafm package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The vulnerability is classified under the SEMVER range, indicating that it affects all versions starting from 0.

How To Fix

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

npm uninstall asatoafm

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 using alternative packages that provide similar functionality without the associated risks. Ensure to review the security status of any alternative packages before integration.

Conclusion

The asatoafm package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is crucial to uninstall this package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.

See every vulnerability recorded for asatoafm →

Share this vulnerability

FAQ

The asatoafm package is an npm library used in JavaScript applications, 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 your application without any signup.

Using the asatoafm package can lead to unauthorized access, data breaches, and exploitation of your application due to the embedded malicious code.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

You should uninstall the asatoafm package immediately and consider using alternative packages that do not have known vulnerabilities.

How To Fix

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

npm uninstall asatoafm

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