Malicious Code Detected in avrtest Package - Security Alert

avrtest Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15211: Malicious code in avrtest (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 avrtest package is an npm library designed for testing purposes, allowing developers to run various test cases efficiently. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package. This vulnerability highlights the importance of scrutinizing third-party packages for potential threats.

Vulnerability Detail

The vulnerability in the avrtest package stems from the inclusion of malicious code that can compromise the integrity and security of applications. This code may lead to unauthorized access, data breaches, or other harmful actions within the software environment. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall avrtest

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, users can avoid using the avrtest package altogether and utilize alternative testing libraries that are known to be secure. Additionally, ensure that your application is monitored for any suspicious activity that may arise from the use of compromised packages.

Conclusion

The discovery of malicious code in the avrtest package underscores the necessity for developers to remain vigilant about the security of third-party libraries. Immediate action is required to mitigate risks associated with this vulnerability, and utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for avrtest →

Share this vulnerability

FAQ

The avrtest package is an npm library used for running test cases in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches within applications using the package.

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

Remove the avrtest package from your project and replace it with a secure alternative. Monitor your application for any suspicious activity.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall avrtest

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