Malicious Code Detected in antishell Package - Security Alert

antishell Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14605: Malicious code in antishell (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 antishell package is an npm library designed for various shell-related functionalities in JavaScript applications. It is often used to enhance command-line interfaces or automate shell commands within Node.js environments. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The antishell package has been found to harbor malicious code that can compromise the security of applications using it. This vulnerability originated from the package's codebase, which was intentionally altered to include harmful scripts. The ramifications of this vulnerability can include unauthorized access to sensitive data, execution of arbitrary code, and potential exploitation of the host system. It is crucial for developers to be aware of this issue and take immediate action to mitigate the risks associated with it.

How To Fix

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

npm uninstall antishell

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 antishell package altogether and implement alternative libraries that provide similar functionalities without the associated risks. For example, consider using 'shelljs' or 'child_process' from Node.js for shell command execution.

Conclusion

The discovery of malicious code in the antishell package highlights the importance of vigilance when using open-source libraries. Developers must take proactive measures to secure their applications by removing vulnerable packages and adopting safer alternatives. Utilizing tools like Vulert can aid in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for antishell →

Share this vulnerability

FAQ

The antishell package is an npm library used for shell-related functionalities in JavaScript applications.

The malicious code can compromise application security, allowing unauthorized access and execution of harmful scripts.

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

It is advised to remove the antishell package immediately and replace it with a secure alternative.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall antishell

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