Malicious Code Detected in closure-es6 Package - MAL-2025-17150

closure-es6 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17150: Malicious code in closure-es6 (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 closure-es6 package is a JavaScript library designed for handling ES6 (ECMAScript 2015) features, enabling developers to write modern JavaScript code. It is widely used in various applications for its ability to simplify code management and enhance performance. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the closure-es6 package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall closure-es6

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, consider removing the closure-es6 package from your project until a secure version is released. You can do this by executing: npm uninstall closure-es6. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The closure-es6 package has been found to contain malicious code, posing a significant threat to applications using it. Users are strongly advised to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor for vulnerabilities in real-time.

See every vulnerability recorded for closure-es6 →

Share this vulnerability

FAQ

The closure-es6 package is a JavaScript library that helps developers work with ES6 features, making it easier to write modern JavaScript code.

The malicious code was identified through security audits and reports from security researchers, including Amazon Inspector.

The risks include unauthorized access to sensitive data, potential data breaches, and the possibility of malicious actions being executed within the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider removing the package as a temporary measure and monitor your application for any signs of exploitation.

How To Fix

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

npm uninstall closure-es6

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