Malicious Code Detected in callin Package - Security Alert

callin Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16461: Malicious code in callin (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'callin' package is a Node.js library designed for handling various functionalities within JavaScript applications. It is commonly used for its ease of integration and utility in managing calls and events. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the 'callin' package, which was introduced in version 0. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The ramifications of this vulnerability include data breaches, loss of integrity, and potential exploitation by malicious actors.

How To Fix

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

npm uninstall callin

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 remove the 'callin' package from your project until a secure version is released. This can be done using the command: 'npm uninstall callin'. Alternatively, consider using a different package that provides similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the 'callin' package highlights the importance of regularly monitoring and updating dependencies in software projects. By taking proactive measures, such as updating to secure versions and utilizing tools like Vulert, developers can safeguard their applications against potential threats.

See every vulnerability recorded for callin →

Share this vulnerability

FAQ

The 'callin' package is a Node.js library used for managing calls and events in JavaScript applications.

The malicious code can allow unauthorized access and manipulation of application data, posing significant security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Yes, it is recommended to update the 'callin' package to the latest secure version to mitigate the vulnerability.

If immediate updates are not possible, consider uninstalling the package or using an alternative library until a secure version is available.

How To Fix

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

npm uninstall callin

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