Critical Security Breach in @vucod/email: Malicious Code Injection Detected

@vucod/email Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191388: Malicious code in @vucod/email (npm). Affects @vucod/email versions 0.0.3. 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 @vucod/email package is an npm library designed for email handling and processing within JavaScript applications. It provides functionalities such as sending emails, managing templates, and integrating with various email services. However, this package has recently been compromised, exposing users to significant security risks due to malicious code embedded within it.

Vulnerability Detail

The vulnerability stems from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which infiltrated the @vucod/email package. This malicious payload is designed to steal sensitive tokens and credentials from users and subsequently publish them to GitHub. Additionally, the worm can propagate itself to other npm packages owned by the user and establish persistence through a GitHub action. There is also a risk that the malicious code could destroy the user's home directory, leading to severe data loss.

How To Fix

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

npm uninstall @vucod/email

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 workaround, you can avoid using the @vucod/email package and consider alternative libraries for email handling until the issue is resolved. Additionally, ensure that your environment is secure by regularly monitoring for any unauthorized access or changes.

Conclusion

The @vucod/email package has been compromised by a malicious worm, posing serious security risks to users. It is essential to take immediate action by updating or removing the package and monitoring your environment for any unauthorized access. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for @vucod/email →

Share this vulnerability

FAQ

The malicious code is designed to steal sensitive information such as tokens and credentials and can also propagate to other npm packages.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If you have installed the @vucod/email package, it is recommended to update it to the latest version or remove it until a secure version is available.

Yes, the malicious code has the potential to destroy the user's home directory, leading to significant data loss.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall @vucod/email

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