Malicious Code Detected in undeface Package - Version 9.9.9

undeface Updated 02 Oct 2025

Summary

02/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6675: Malicious code in undeface (npm). Affects undeface versions 9.9.9. 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 'undeface' package is an npm library that is used for various functionalities in JavaScript applications. It is designed to facilitate certain operations within the codebase, but it has been identified as having malicious behavior in version 9.9.9. This vulnerability poses a risk to developers and users who rely on this package for their applications.

Vulnerability Detail

The vulnerability in the 'undeface' package arises from its communication with a domain associated with malicious activity. This behavior can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The package was flagged by the OpenSSF Package Analysis project, which identified its malicious nature based on its interactions with harmful domains.

How To Fix

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

npm uninstall undeface

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

If you cannot update the package immediately, consider removing it from your project and replacing it with an alternative library that provides similar functionality without the associated risks.

Conclusion

The 'undeface' package version 9.9.9 has been identified as malicious due to its communication with harmful domains. It is crucial for developers to update to a safe version or find alternatives to mitigate risks associated with this vulnerability. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for undeface →

Share this vulnerability

FAQ

The 'undeface' package is an npm library used in JavaScript applications for various coding functionalities.

Version 9.9.9 is flagged as malicious because it communicates with a domain linked to harmful activities, posing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider removing the 'undeface' package and using an alternative library that does not have known vulnerabilities.

Vulert provides real-time monitoring and alerts for open-source vulnerabilities using your package-lock.json, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall undeface

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