Critical Malicious Code Vulnerability in core.trigger Package

core.trigger Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6409: Malicious code in core.trigger (npm). Affects core.trigger versions 1.0.0. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The core.trigger package is an npm module designed for event handling and triggering actions within JavaScript applications. It is commonly used for managing asynchronous events and enhancing user interactions. However, this package has been identified to contain malicious code that could compromise the security of applications utilizing it, making it essential for developers to be aware of this vulnerability.

Vulnerability Detail

The vulnerability identified as MAL-2025-6409 originates from a malicious code injection in version 1.0.0 of the core.trigger package. This code can lead to unauthorized access, data breaches, or even complete takeover of the affected application. The malicious code was discovered by ReversingLabs and is part of a broader trend of compromised npm packages that pose significant risks to developers and end-users alike.

How To Fix

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

npm uninstall core.trigger

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, developers are advised to remove the core.trigger package from their dependencies until a secure version is released. This can be done using the command: npm uninstall core.trigger.

Conclusion

The core.trigger package has been identified with a critical vulnerability due to malicious code injection. Developers must take immediate action to protect their applications by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for core.trigger →

Share this vulnerability

FAQ

core.trigger is an npm package used for event handling in JavaScript applications, allowing developers to manage asynchronous events effectively.

The MAL-2025-6409 vulnerability involves malicious code that can compromise application security, leading to potential data breaches or unauthorized access.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected. Visit Vulert Scanner for a quick assessment without signup.

Currently, there is no patched version of the core.trigger package available. It is recommended to monitor the npm registry for updates.

If you are using the core.trigger package, it is advisable to uninstall it until a secure version is released. Use the command: npm uninstall core.trigger.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall core.trigger

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