Malicious Code Vulnerability in @ads-core/types Package

@ads-core/types Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192700: Malicious code in @ads-core/types (npm). Affects @ads-core/types versions 11.7.7 – 11.7.9. 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 @ads-core/types package is a library used in JavaScript applications, primarily for defining and managing types in a structured manner. It is commonly utilized in projects that require type safety and improved code maintainability. However, recent findings have revealed that certain versions of this package contain malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code in specific versions of the @ads-core/types package, particularly versions 11.7.7 and 11.7.9. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected applications. The origin of this vulnerability is linked to the package being compromised, which can have severe ramifications for developers and users alike, including loss of sensitive information and trust in the software supply chain.

How To Fix

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

npm uninstall @ads-core/types

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 affected versions of the @ads-core/types package from your project and avoid using any functionality that relies on it until a secure version is confirmed. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the @ads-core/types package highlights the importance of vigilance in managing open-source dependencies. By updating to secure versions and utilizing tools like Vulert, developers can protect their applications from potential threats.

See every vulnerability recorded for @ads-core/types →

Share this vulnerability

FAQ

The affected versions are 11.7.7 and 11.7.9.

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.

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

Using the compromised package can lead to unauthorized access, data breaches, and exploitation of your application, potentially harming users and damaging your reputation.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions to minimize the risk of vulnerabilities.

How To Fix

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

npm uninstall @ads-core/types

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