Malicious Code in purchase (npm)

purchase Updated 02 Oct 2025

Summary

23/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8601: Malicious code in purchase (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'purchase' package is an npm package used for purchasing functionality in software applications. It provides a set of APIs and tools to handle purchase transactions and related operations. The package is widely used in various projects and is a critical component for handling financial transactions. However, the package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The 'purchase' package has been compromised with malicious code. This code can give full control of the affected computer to an external entity. As a result, all secrets and keys stored on the compromised computer should be rotated immediately from a different computer. Removing the package may not guarantee the removal of all malicious software installed as a result of its installation. The presence of this package on a computer should be considered a complete compromise, and immediate action is required to mitigate the potential risks.

How To Fix

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

npm uninstall purchase

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

There is no specific workaround provided for this vulnerability. The best course of action is to follow the steps mentioned in the 'how_to_fix' section and take immediate action to remove the 'purchase' package and rotate all secrets and keys.

Conclusion

The 'purchase' package has been compromised with malicious code, posing a significant security risk to any computer that has it installed or running. Immediate action is required to remove the package, rotate secrets and keys, and perform a thorough security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for purchase →

Share this vulnerability

FAQ

The 'purchase' package is an npm package used for handling purchase functionality in software applications. It provides APIs and tools for managing purchase transactions and related operations.

The malicious code in the 'purchase' package can give full control of the affected computer to an external entity. This compromises the security of the computer and puts all stored secrets and keys at risk.

If you have the 'purchase' package installed on your computer, it is crucial to take immediate action. Remove the package, rotate all secrets and keys stored on the compromised computer from a different, secure computer, and perform a thorough security audit to identify and mitigate any potential damage.

Removing the 'purchase' package may not guarantee the complete removal of all malicious software installed as a result of its installation. It is recommended to perform a thorough security audit and investigation to ensure all traces of the compromise are eliminated.

To prevent similar vulnerabilities in the future, it is essential to regularly update and patch all software components, including third-party packages. Additionally, conducting security audits and using tools like Vulert can help identify and mitigate potential risks.

How To Fix

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

npm uninstall purchase

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