Malicious Code in vetx (npm)

vetx Updated 02 Oct 2025

Summary

09/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8497: Malicious code in vetx (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 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 vetx package is an npm package used for [provide brief description of the package's functionality and key attributes]. It is vulnerable to a malicious code injection attack, which compromises the security of any computer that has this package installed or running. The attack allows an outside entity to gain full control of the computer, potentially leading to unauthorized access to sensitive information and the need to rotate all secrets and keys stored on the compromised machine.

Vulnerability Detail

The vulnerability, identified as MAL-2023-8497, originates from the ghsa-malware source. The malicious code injected into the vetx package poses a significant threat to the security of the affected computer. It is highly recommended to consider any machine with this package installed as fully compromised. Removing the package may not guarantee the removal of all malicious software resulting from its installation. The CWE-506 classification is assigned to this vulnerability, indicating the presence of embedded malicious code.

How To Fix

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

npm uninstall vetx

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 mentioned for this vulnerability. However, it is essential to follow the steps outlined in the 'how_to_fix' section to mitigate the risk and secure the affected computer.

Conclusion

The presence of malicious code in the vetx package poses a significant security risk to any computer with this package installed or running. It is crucial to take immediate action by rotating all secrets and keys, removing the package, conducting a security audit, and implementing additional security measures. For further support and guidance, contact DevNack.com.

See every vulnerability recorded for vetx →

Share this vulnerability

FAQ

The impact of this vulnerability is severe, as it allows an outside entity to gain full control of the affected computer. This can lead to unauthorized access to sensitive information and the need to rotate all secrets and keys stored on the compromised machine.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using only the package-lock.json file.

No, there is no guarantee that removing the vetx package will remove all malicious software resulting from its installation. It is recommended to conduct a thorough security audit to identify any potential unauthorized access or data breaches.

To prevent such vulnerabilities, it is recommended to regularly update and patch software, use strong passwords, and employ multi-factor authentication. Conducting security audits and monitoring for open-source vulnerabilities using tools like Vulert can also enhance security.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide expert guidance and assistance in securing your systems.

How To Fix

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

npm uninstall vetx

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