Malicious Code Detected in adrum Package - Security Alert

adrum Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14115: Malicious code in adrum (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 adrum package is a JavaScript library commonly used in web applications for performance monitoring and analytics. It provides developers with tools to track user interactions and application performance metrics. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the adrum package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, facilitate data exfiltration, or enable other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall adrum

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 measure, consider removing the adrum package from your project until a secure version is released. You can do this by running the following command: 'npm uninstall adrum'. This will help mitigate the risk of exploitation while you await a fix.

Conclusion

The discovery of malicious code in the adrum package poses a serious threat to applications utilizing this library. Developers are urged to take immediate action by updating or removing the package until a secure version is released. Continuous monitoring and vulnerability management are essential to maintain application security.

See every vulnerability recorded for adrum →

Share this vulnerability

FAQ

The adrum package is used for performance monitoring and analytics in web applications, helping developers track user interactions and application performance.

The malicious code was identified through security audits and monitoring by security tools, including Amazon Inspector.

The malicious code could lead to unauthorized access to sensitive data, data exfiltration, or other harmful activities within affected applications.

Currently, there is no patched version available. It is crucial to monitor the package repository for updates and apply them as soon as they are released.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.

How To Fix

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

npm uninstall adrum

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