Malicious Code Detected in glossa Package - Security Alert

glossa Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21587: Malicious code in glossa (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The glossa package is an npm library designed for various functionalities within JavaScript applications. It is utilized for its features that enhance user experience and streamline development processes. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the glossa package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, and potential exploitation of user data. The malicious nature of this vulnerability was identified by Amazon Inspector, indicating a serious threat to developers and users alike.

How To Fix

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

npm uninstall glossa

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 measure, consider removing the glossa package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall glossa'. This will help mitigate the risks associated with the malicious code until a fix is implemented.

Conclusion

The discovery of malicious code in the glossa package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for glossa →

Share this vulnerability

FAQ

The glossa package is an npm library that provides various functionalities to enhance JavaScript applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can identify if your application is affected.

If immediate updates are not feasible, consider uninstalling the glossa package as a temporary workaround to protect your application.

The malicious code in the glossa package was identified by Amazon Inspector, a security tool that helps detect vulnerabilities in software.

You can find detailed information about this vulnerability on the GitHub repository of the Open Source Vulnerability database.

How To Fix

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

npm uninstall glossa

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