Malicious Code Detected in admin10001 Package: Version 1.0.10 Compromised

admin10001 Updated 16 Jan 2026

Summary

16/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-322: Malicious code in admin10001 (npm). Affects admin10001 versions 1.0.0 – 1.0.8. 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

The admin10001 package is an npm module designed for administrative tasks within JavaScript applications. It provides various functionalities that assist developers in managing their applications efficiently. However, this package has been flagged for malicious behavior, specifically in version 1.0.10, which communicates with a domain linked to malicious activities and executes harmful commands.

Vulnerability Detail

The vulnerability in the admin10001 package arises from its ability to connect to a malicious domain and execute commands that can compromise the security of the host system. This behavior poses significant risks, including unauthorized access to sensitive data, potential system damage, and exploitation of the affected environment. The malicious nature of this package was identified by the OpenSSF Package Analysis project, which monitors and evaluates the safety of open-source packages.

How To Fix

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

npm uninstall admin10001

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, you can remove the admin10001 package from your project to mitigate the risk of exploitation. Use the following command to uninstall the package: npm uninstall admin10001. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The admin10001 package has been identified as malicious, particularly in version 1.0.10. Users are advised to update to a patched version or remove the package to safeguard their applications. Continuous monitoring of open-source dependencies is crucial to maintaining security.

See every vulnerability recorded for admin10001 →

Share this vulnerability

FAQ

admin10001 is an npm package designed for administrative tasks in JavaScript applications, but it has been flagged for malicious behavior.

The vulnerability was identified by the OpenSSF Package Analysis project, which monitors open-source packages for security issues.

The risks include unauthorized access to sensitive data, potential system damage, and exploitation of the affected environment.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code.

If immediate updates are not possible, consider uninstalling the package as a temporary workaround to prevent exploitation.

How To Fix

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

npm uninstall admin10001

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