Malicious Code Detected in arthur-lib: A Critical Vulnerability

arthur-lib Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14871: Malicious code in arthur-lib (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

arthur-lib is an npm package designed for various utility functions in JavaScript applications. It is widely used for its simplicity and effectiveness in enhancing application performance. However, it has been found to contain malicious code that compromises the security of applications utilizing this package.

Vulnerability Detail

The vulnerability in arthur-lib stems from the inclusion of malicious code within the package. This code can lead to unauthorized access, data breaches, or other harmful actions within the applications that depend on it. The malicious code was introduced in version 0 and affects all subsequent versions, posing a significant risk to developers and users alike.

How To Fix

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

npm uninstall arthur-lib

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, consider replacing arthur-lib with alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any package before integrating it into your project.

Conclusion

The discovery of malicious code in the arthur-lib npm package poses a serious threat to developers and users. Immediate action is required to mitigate the risks associated with this vulnerability. By uninstalling the package and monitoring for updates, you can protect your applications from potential harm.

See every vulnerability recorded for arthur-lib →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within applications, potentially leading to data breaches or other security incidents.

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 identify if your application is affected.

The best mitigation strategy is to uninstall arthur-lib and replace it with a secure alternative. Avoid using the package until a patched version is released.

If your application is already deployed with arthur-lib, it is crucial to remove the package immediately and monitor for any unusual activity or security breaches.

You can visit Vulert's website for more information on monitoring open-source vulnerabilities and how to secure your applications.

How To Fix

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

npm uninstall arthur-lib

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