Malicious Package in test-module-a

test-module-a Updated 02 Oct 2025

Summary

11/09/2020
CRITICAL
No i
Critical
9.8

GHSA-76xq-58hj-vwm2: Malicious Package in test-module-a. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The test-module-a package is an npm package that is used for testing purposes. It is designed to assist developers in testing their applications by providing various functionalities and utilities. However, all versions of test-module-a contain a critical vulnerability that allows for package hijacking. This vulnerability is due to the presence of malicious code in the package's preinstall script.

Vulnerability Detail

The vulnerability in test-module-a arises from the malicious code present in its preinstall script. When the package is installed, the preinstall script fetches the names of all npm packages owned by the user. It then attempts to add another maintainer to every package, effectively hijacking them. This can lead to unauthorized access and control over the compromised packages. The impact of this vulnerability can be severe, as it allows an attacker to gain control over a wide range of packages and potentially exploit them for malicious purposes.

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 →

Conclusion

The test-module-a package contains a critical vulnerability that allows for package hijacking. It is recommended to remove the package from your system and contact npm security if any of your packages were compromised. Enabling two-factor authentication (2FA) for publishing can provide further security for your maintained packages. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for test-module-a →

Share this vulnerability

FAQ

The test-module-a package is an npm package used for testing purposes. It provides various utilities and functionalities to assist developers in testing their applications.

The vulnerability in test-module-a allows for package hijacking, which can lead to unauthorized access and control over compromised packages. This can have severe consequences, as it enables attackers to exploit the compromised packages for malicious purposes.

To fix the vulnerability, remove the test-module-a package from your system. If you own any compromised packages, contact npm security immediately at security@npmjs.com. Additionally, enable two-factor authentication (2FA) for publishing to further secure your maintained packages.

No, there is no known workaround for this vulnerability. The recommended course of action is to remove the test-module-a package and follow the steps mentioned to fix the vulnerability.

To prevent similar vulnerabilities, it is essential to regularly update your packages to the latest versions. Stay informed about security advisories and promptly apply any necessary patches or fixes. Additionally, consider using tools like Vulert (https://vulert.com) to monitor and alert for open-source vulnerabilities in your software.

Related vulnerabilities

Recent vulnerabilities recorded for test-module-a.

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