Malicious Code Detected in cassback: A Critical npm Vulnerability

cassback Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16628: Malicious code in cassback (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 package 'cassback' is an npm library designed to facilitate callback functions in JavaScript applications. It is commonly used for managing asynchronous operations, providing developers with a streamlined way to handle multiple callbacks. 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 'cassback' package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall cassback

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 avoid using the 'cassback' package in your application until a secure alternative is identified. Review your codebase to ensure that no dependencies rely on 'cassback'.

Conclusion

The discovery of malicious code in the 'cassback' npm package poses a serious threat to applications that utilize it. Immediate action is required to uninstall the package and replace it with a secure alternative. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time, ensuring the safety of your software.

See every vulnerability recorded for cassback →

Share this vulnerability

FAQ

The cassback package is an npm library used for managing callback functions in JavaScript applications.

The malicious code in cassback can lead to unauthorized access and potential data breaches in applications that use it.

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

No, there is currently no patch available for the cassback package. It is recommended to uninstall it and seek alternative packages.

You should uninstall the cassback package immediately and review your code for any potential security issues caused by its use.

How To Fix

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

npm uninstall cassback

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