Malicious Code in saml-mock-idp (npm)

saml-mock-idp Updated 02 Oct 2025

Summary

12/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8332: Malicious code in saml-mock-idp (npm). Affects saml-mock-idp versions 1.0.0. 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 saml-mock-idp package is an npm package that provides a mock Identity Provider (IdP) for testing purposes. It allows developers to simulate SAML-based authentication flows in their applications. The package is widely used in the Node.js ecosystem for testing SAML integrations and ensuring the correct behavior of SAML service providers. However, a recent analysis by the OpenSSF Package Analysis project has identified version 1.0.0 of saml-mock-idp as malicious.

Vulnerability Detail

The saml-mock-idp package has been flagged as malicious because it communicates with a domain associated with malicious activity. This behavior raises concerns about the security and integrity of the package. If developers unknowingly use this version of saml-mock-idp, it could potentially expose their applications to various security risks, including data breaches, unauthorized access, and potential compromise of user credentials.

How To Fix

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

npm uninstall saml-mock-idp

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 →

Conclusion

In conclusion, version 1.0.0 of the saml-mock-idp npm package has been identified as malicious. It is crucial for developers to avoid using this version and upgrade to a newer, non-malicious version to mitigate potential security risks. Regularly updating dependencies and using security tools like Vulert can help ensure the overall security of your application. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for saml-mock-idp →

Share this vulnerability

FAQ

saml-mock-idp is an npm package that provides a mock Identity Provider (IdP) for testing SAML integrations in Node.js applications.

Using version 1.0.0 of saml-mock-idp can potentially expose your application to security risks, including data breaches and unauthorized access.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you if any open-source vulnerabilities, including this one, are detected.

Yes, the recommended fix is to upgrade to a newer version of the saml-mock-idp package that is not flagged as malicious.

To ensure the security of your dependencies, it is important to regularly update them to the latest non-malicious versions. Additionally, using a tool like Vulert can help you monitor and alert you in real-time for any open-source vulnerabilities in your software.

How To Fix

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

npm uninstall saml-mock-idp

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