Malicious Code Detected in anionic Package - Security Alert

anionic Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14544: Malicious code in anionic (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The anionic package is a JavaScript library used in various applications to facilitate specific functionalities related to web development. It is commonly utilized in npm environments for its ease of integration and utility. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the anionic package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions that could affect the integrity of the software. The malicious nature of this vulnerability is particularly concerning as it can be exploited without the user's knowledge, potentially leading to severe consequences.

How To Fix

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

npm uninstall anionic

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 anionic package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall anionic'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the anionic package highlights the importance of vigilance in software development. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for anionic →

Share this vulnerability

FAQ

The anionic package is a JavaScript library used in web development, primarily within npm environments.

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

You can use Vulert to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check if your application is affected without any signup.

If you are using anionic, it is recommended to uninstall the package immediately and await a patched version.

Regularly check the official repositories of the packages you use and consider using tools like Vulert for real-time monitoring.

How To Fix

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

npm uninstall anionic

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