Malicious Code Detected in engility Package - Security Alert

engility Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19655: Malicious code in engility (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The engility package is an npm library designed for various functionalities within JavaScript applications. It is utilized for its ease of integration and efficiency in handling specific tasks. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the engility package, which was introduced in version 0. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package's codebase, which has been tampered with to include harmful scripts.

How To Fix

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

npm uninstall engility

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 engility package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement security measures such as code reviews and dependency scanning to mitigate potential threats.

Conclusion

The discovery of malicious code in the engility package poses a serious threat to applications that utilize it. It is crucial for developers to take immediate action by removing the package and seeking alternatives. Utilizing tools like Vulert can help in monitoring for vulnerabilities and ensuring the security of your applications.

See every vulnerability recorded for engility →

Share this vulnerability

FAQ

Engility is an npm package used in JavaScript applications for various functionalities, but it has recently been found to contain malicious code.

You can use tools like Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.

If you are using the engility package, it is recommended to remove it immediately and look for secure alternatives. Additionally, keep your dependencies updated.

Currently, there is no patched version of the engility package available. It is best to remove the package until a secure alternative is found.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed about potential risks.

How To Fix

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

npm uninstall engility

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