Critical Malicious Code Vulnerability in acios.js Package

acios.js Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5884: Malicious code in acios.js (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The acios.js package is a JavaScript library used in Node.js applications for various functionalities. It is designed to facilitate certain operations within the npm ecosystem. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability in acios.js is characterized by the presence of embedded malicious code that can lead to complete system compromise. This code can potentially allow unauthorized access to sensitive data, including secrets and keys stored on the affected machine. The vulnerability originates from the package itself and affects all versions starting from its introduction. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall acios.js

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you have a backup of your project before proceeding with the removal.

Conclusion

The acios.js package poses a critical security risk due to embedded malicious code. Users must take immediate action to remove the package and secure their systems. Regular monitoring for vulnerabilities using tools like Vulert can help prevent future incidents.

See every vulnerability recorded for acios.js →

Share this vulnerability

FAQ

You should remove the acios.js package immediately and rotate any sensitive information stored on the affected system.

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

Currently, there is no patch available. The best course of action is to remove the package entirely.

Failing to remove acios.js can lead to unauthorized access to sensitive data and complete compromise of the system.

It is highly discouraged to reinstall acios.js due to its known malicious nature. Look for alternative packages that provide similar functionality.

How To Fix

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

npm uninstall acios.js

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