Malicious Code Detected in angularjs-in-view Package

angularjs-in-view Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14537: Malicious code in angularjs-in-view (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 angularjs-in-view package is a JavaScript library designed to facilitate the detection of elements entering or exiting the viewport in web applications. It is commonly used in conjunction with AngularJS to enhance user experience by triggering events based on visibility. However, this package has been found to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the angularjs-in-view package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or lead to further exploitation of the application. The issue is particularly concerning as it 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 angularjs-in-view

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, you can prevent the use of the angularjs-in-view package by removing it from your dependencies and replacing it with a different library that provides similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the angularjs-in-view package poses a significant threat to applications that utilize it. Developers are urged to take immediate action by removing the package and seeking secure alternatives to protect their applications from potential exploitation.

See every vulnerability recorded for angularjs-in-view →

Share this vulnerability

FAQ

It is a JavaScript library used to detect when elements enter or exit the viewport in web applications.

The malicious code can potentially allow unauthorized access to sensitive data or execute arbitrary commands.

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

You should remove the angularjs-in-view package from your project and consider using a secure alternative.

Currently, there is no patched version available, and it is recommended to remove the package until a secure alternative is found.

How To Fix

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

npm uninstall angularjs-in-view

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