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

amadkuen Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170798: Malicious code in amadkuen (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 amadkuen package is part of the npm ecosystem, which is widely used for JavaScript package management. It is typically utilized by developers to manage dependencies in their applications. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing features, leading to potential security risks for users who inadvertently install it.

Vulnerability Detail

The vulnerability in the amadkuen package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, inflate developer reputation scores fraudulently, and expose users to further malicious code if they install these derivative packages.

How To Fix

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

npm uninstall amadkuen

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 avoid using the amadkuen package and any packages that may have been published as derivatives. Regularly audit your package-lock.json file for any suspicious entries and remove any unrecognized packages.

Conclusion

The amadkuen package poses a significant risk due to its malicious code designed to exploit npm's publishing features. Users are advised to uninstall this package and monitor their dependencies closely to maintain the security of their applications.

See every vulnerability recorded for amadkuen →

Share this vulnerability

FAQ

The amadkuen package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If you have the amadkuen package installed, your application may be at risk of incorporating malicious code and could potentially lead to security breaches.

You should uninstall the amadkuen package immediately using 'npm uninstall amadkuen' and review your dependencies for any other suspicious packages.

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 amadkuen

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