Malicious Code Detected in @3kali182/angular-1.6: A Security Threat

@3kali182/angular-1.6 Updated 02 Oct 2025

Summary

11/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5834: Malicious code in @3kali182/angular-1.6 (npm). Affects @3kali182/angular-1.6 versions 9.1.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package @3kali182/angular-1.6 is a version of AngularJS, a popular JavaScript framework used for building web applications. This specific package version, 9.1.1, has been flagged for malicious behavior, which can compromise the security of applications that utilize it. The vulnerability arises from the package's ability to communicate with domains associated with malicious activities and execute harmful commands.

Vulnerability Detail

The vulnerability in @3kali182/angular-1.6 originates from its malicious code that allows it to interact with harmful domains and execute commands that can lead to unauthorized access or data breaches. This poses significant risks to applications relying on this package, potentially leading to data theft, system compromise, or further exploitation of the application environment.

How To Fix

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

npm uninstall @3kali182/angular-1.6

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

If immediate updating is not possible, consider removing the package from your project and replacing it with a trusted alternative. You can do this by running: 'npm uninstall @3kali182/angular-1.6'.

Conclusion

The @3kali182/angular-1.6 package has been identified as malicious, posing significant security risks to applications that utilize it. Immediate action is required to update or remove the package to safeguard your application from potential threats.

See every vulnerability recorded for @3kali182/angular-1.6 →

Share this vulnerability

FAQ

The package communicates with domains linked to malicious activities and executes harmful commands.

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

Consider removing the package and replacing it with a trusted alternative to mitigate the risk.

Currently, the malicious version is 9.1.1. Updating to a secure version is necessary as the malicious behavior is confirmed in this version.

Using this package can lead to unauthorized access, data breaches, and exploitation of your application environment.

How To Fix

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

npm uninstall @3kali182/angular-1.6

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