Critical Vulnerability in harmlesspackage

harmlesspackage Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.8

GHSA-8hmr-w35f-3qgj: Malicious Package in harmlesspackage. Affects harmlesspackage 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 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

harmlesspackage is an npm package that provides functionality for XYZ. It is widely used in various applications and has a version 0.0.1. The package has been found to contain a critical vulnerability in its postinstall script. This vulnerability allows an attacker to execute malicious code during the package installation process.

Vulnerability Detail

The version 0.0.1 of harmlesspackage includes a postinstall script that prints a message to the console and performs a GET request to a remote server. This behavior is unauthorized and can lead to potential compromise of the system. The package has been flagged as malicious, and it is recommended to remove it from the environment to prevent any further compromise.

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

In conclusion, harmlesspackage version 0.0.1 contains a critical vulnerability that allows unauthorized code execution during package installation. It is recommended to remove the package from the environment to prevent any further compromise. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for harmlesspackage →

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute unauthorized code during the package installation process, potentially compromising the system.

There is no evidence of further compromise beyond the unauthorized code execution during the package installation.

The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

No, only version 0.0.1 of harmlesspackage is affected by this vulnerability.

Yes, the fix for this vulnerability is to remove the package from the environment.

Related vulnerabilities

Recent vulnerabilities recorded for harmlesspackage.

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