Critical Vulnerability in only-test-not-install Package

only-test-not-install Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.8

GHSA-g9wf-393q-4w38: Malicious Package in only-test-not-install. Affects only-test-not-install versions >= 0.0.0. 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 only-test-not-install package is an npm package used for testing purposes. It allows developers to run tests without actually installing the package. This package is commonly used in development environments to streamline the testing process. However, all versions of the only-test-not-install package contain a critical vulnerability that can lead to the deletion of the system's test folder during the postinstall script execution.

Vulnerability Detail

The vulnerability in the only-test-not-install package arises from malicious code present in all versions. When the package is installed, it executes a postinstall script that deletes the folder '~/test' from the system. This can have severe consequences as it may result in the loss of important test files and disrupt the testing process. The presence of this vulnerability poses a significant risk to the integrity and reliability of the development environment.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to remove the package from the environment to mitigate the risk of data loss.

Conclusion

The only-test-not-install package contains a critical vulnerability that can lead to the deletion of the system's test folder. To mitigate this risk, it is recommended to remove the package from your environment. If you need further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for only-test-not-install →

Share this vulnerability

FAQ

The only-test-not-install package is used for running tests without actually installing the package. It is commonly used in development environments to streamline the testing process.

The vulnerability in the only-test-not-install package can result in the deletion of the system's test folder. This can lead to the loss of important test files and disrupt the testing process in the development environment.

To fix this vulnerability, you should remove the only-test-not-install package from your environment by running the command 'npm uninstall only-test-not-install'.

No, there is no known workaround for this vulnerability. It is crucial to remove the package from the environment to mitigate the risk of data loss.

Related vulnerabilities

Recent vulnerabilities recorded for only-test-not-install.

How To Fix

No fixed version is published for this vulnerability.

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