Critical Malicious Code Vulnerability in amprem Package

amprem Updated 12 Oct 2026

Summary

12/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17815: Malicious code in amprem (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 amprem package is a Node.js library available through npm, designed to facilitate various functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses significant risks, including unauthorized access to sensitive data and control over the affected system.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the amprem package. This code can lead to a complete compromise of any computer running the package, allowing attackers to access secrets and keys stored on the system. The origin of this vulnerability has been traced back to a malicious actor who introduced harmful code into the package, which is classified under CWE-506, indicating that it contains code that appears to be malicious in nature. 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 amprem

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 to mitigate the risks posed by the amprem package. The only recommended action is to completely remove the package from your system.

Conclusion

The amprem package has been identified as containing malicious code that poses serious security risks. Users are strongly advised to uninstall the package and take necessary precautions to secure their systems. Continuous monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for amprem →

Share this vulnerability

FAQ

The amprem package is a Node.js library available on npm, used for various functionalities in JavaScript applications.

The malicious code can lead to unauthorized access to sensitive data and complete control over the affected system.

You should immediately uninstall the amprem package and rotate any secrets or keys stored on your system.

No, there is no patch available for the amprem package. The only solution is to remove it from your system.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall amprem

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