Malicious Code Injection in amandasmith Package: A Threat to npm Users

amandasmith Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170799: Malicious code in amandasmith (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The amandasmith package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code among developers. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the amandasmith package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry. The malicious payload can lead to unintended consequences for developers, including the risk of using compromised packages and potential security breaches in their applications.

How To Fix

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

npm uninstall amandasmith

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 amandasmith package from your project by executing the command: 'npm uninstall amandasmith'. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The amandasmith package poses a significant risk due to its malicious code injection vulnerability. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for amandasmith →

Share this vulnerability

FAQ

The amandasmith package is a JavaScript package available on npm, used for various development purposes. However, it has been identified as part of a malicious campaign.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.

If you have installed amandasmith, it is recommended to uninstall it immediately and check for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall amandasmith

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