Critical Malicious Code Vulnerability in trial-guard Package

trial-guard Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192764: Malicious code in trial-guard (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 trial-guard package is an npm library designed to provide trial management functionalities for applications. It allows developers to implement trial periods for their software products, enabling users to experience features before making a purchase. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the trial-guard package, identified by the alias GHSA-vjg7-9cf4-mpp8. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the system may have been granted to an external entity.

How To Fix

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

npm uninstall trial-guard

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

There are no specific workarounds available for this vulnerability other than removing the package and securing your system. Ensure that you monitor your system for any unusual activity following the removal.

Conclusion

The trial-guard package has been compromised with malicious code, posing serious security threats to any system using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate risks. Utilize tools like Vulert to monitor your applications for vulnerabilities.

See every vulnerability recorded for trial-guard →

Share this vulnerability

FAQ

Immediately uninstall the trial-guard package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

No, there is currently no patched version of the trial-guard package available.

Failing to remove the package could lead to unauthorized access to your system and potential data breaches.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, allowing you 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 trial-guard

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