Malicious Code Detected in Angular-Truncate Package - Security Alert

angular-truncate Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14532: Malicious code in angular-truncate (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 angular-truncate package is a popular npm library used for truncating text in Angular applications. It provides developers with an easy way to manage text overflow and enhance user interface design. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the angular-truncate package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall angular-truncate

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 angular-truncate package from your project until a secure version is released. You can do this by running: 'npm uninstall angular-truncate'. Alternatively, you may explore other libraries that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the angular-truncate package highlights the importance of maintaining secure dependencies in software development. Developers are urged to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for angular-truncate →

Share this vulnerability

FAQ

The angular-truncate package is used to truncate text in Angular applications, helping manage text overflow effectively.

The malicious code found in angular-truncate can lead to unauthorized access and potential data breaches in applications that use this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Yes, you can mitigate risks by uninstalling the angular-truncate package or replacing it with a safer alternative until a patched version is available.

It is advisable to regularly check for vulnerabilities in your dependencies, ideally as part of your continuous integration/continuous deployment (CI/CD) process.

How To Fix

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

npm uninstall angular-truncate

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