Critical Malicious Code Vulnerability in amarium Package

amarium Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14421: Malicious code in amarium (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 amarium package is a JavaScript library available through the npm ecosystem, designed for various functionalities in web development. It is widely used due to its ease of integration and utility in enhancing application performance. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the amarium package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, and potential exploitation of user data. The malicious nature of this vulnerability makes it critical for developers to address it promptly to safeguard their applications.

How To Fix

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

npm uninstall amarium

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, you can remove the amarium package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall amarium.

Conclusion

The amarium package has been identified to contain malicious code, posing significant security risks. Developers are urged to take immediate action by updating or uninstalling the package to protect their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for amarium →

Share this vulnerability

FAQ

The amarium package is a JavaScript library used in web development, providing various functionalities to enhance application performance.

The malicious code can lead to unauthorized access and data breaches, compromising the security of applications that utilize the package.

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.

Currently, there is no specific patched version mentioned. It is advisable to monitor the npm registry for updates and patches.

If immediate updates are not possible, consider uninstalling the amarium package as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall amarium

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