Malicious Code Detected in fullcube-angular-base Package

fullcube-angular-base Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21037: Malicious code in fullcube-angular-base (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 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 fullcube-angular-base package is a library used in Angular applications, providing essential functionalities for developers. However, it has been identified to contain malicious code, posing a significant risk to applications utilizing this package. The malicious code can compromise application security, leading to potential data breaches or unauthorized access.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the fullcube-angular-base package. This code can execute harmful actions, such as data exfiltration or unauthorized access to user information. The origin of this vulnerability is linked to the package's version 0 and earlier, which lacks the necessary security measures to prevent such exploits. The ramifications of this vulnerability can be severe, affecting not only the integrity of the application but also the security of its users.

How To Fix

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

npm uninstall fullcube-angular-base

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 fullcube-angular-base package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall fullcube-angular-base'. This will help mitigate the risk of malicious code execution in your application.

Conclusion

The fullcube-angular-base package has been identified to contain malicious code, posing significant risks to applications that utilize it. It is crucial to update or remove the package to safeguard your application and its users. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for fullcube-angular-base →

Share this vulnerability

FAQ

fullcube-angular-base is an npm package used in Angular applications to provide various functionalities for developers.

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

Using the compromised fullcube-angular-base package can lead to data breaches, unauthorized access to user information, and overall application instability.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities without requiring code access or installation. You can check your application using the Vulert playground.

If immediate updates are not possible, consider removing the package temporarily and monitoring for any security patches or updates from the maintainers.

How To Fix

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

npm uninstall fullcube-angular-base

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