Malicious Code Injection in veyto Package: A Threat to npm Ecosystem

veyto Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91762: Malicious code in veyto (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 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

The veyto package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful packages, potentially compromising the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability in the veyto package stems from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to the continuous republishing of these malicious variants. The ramifications include the pollution of the npm registry and the risk of developers inadvertently incorporating these compromised packages into their projects.

How To Fix

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

npm uninstall veyto

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

As a temporary measure, you can avoid using the veyto package until a secure version is released. Additionally, consider using package-lock.json to monitor your dependencies for vulnerabilities. Tools like Vulert can help you identify and alert you about open-source vulnerabilities in your software without requiring code access or installation.

Conclusion

The veyto package has been identified as part of a malicious campaign that poses a significant risk to the npm ecosystem. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their projects. Regularly updating dependencies and utilizing monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for veyto →

Share this vulnerability

FAQ

The veyto package is a JavaScript package used within the npm ecosystem for various development purposes, but it has been compromised by malicious actors.

If your project uses the veyto package, it may inadvertently include malicious code that can compromise your application's security and integrity.

You should immediately update the package to the latest version or remove it from your project until a secure version is available.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall veyto

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