Malicious Code Detected in chime-secrets Package - Vulnerability Overview

chime-secrets Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6079: Malicious code in chime-secrets (npm). Affects chime-secrets 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 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 chime-secrets package is an npm library designed for managing secrets in applications, particularly those that utilize Amazon Chime services. It provides functionalities for securely handling sensitive information. However, this package has been identified as having a vulnerability that allows it to communicate with a domain associated with malicious activities, posing a risk to users and their applications.

Vulnerability Detail

The vulnerability in the chime-secrets package originates from its ability to connect to a malicious domain. This could lead to unauthorized data access, data exfiltration, or other malicious activities that compromise the integrity and security of applications using this package. The issue was introduced in version 1.0.0 and continues to affect all subsequent versions.

How To Fix

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

npm uninstall chime-secrets

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 chime-secrets package from your project until a secure version is released. You can do this by running the command: 'npm uninstall chime-secrets'. This will prevent any potential malicious activity while you seek an alternative solution.

Conclusion

The chime-secrets package has a significant vulnerability that allows it to connect to a malicious domain, posing risks to applications that utilize it. Users are advised to update or remove the package until a secure version is available. Monitoring tools like Vulert can assist in identifying vulnerabilities in your application.

See every vulnerability recorded for chime-secrets →

Share this vulnerability

FAQ

The chime-secrets package is used for managing secrets in applications that utilize Amazon Chime services, ensuring sensitive information is handled securely.

The vulnerability allows the package to communicate with a malicious domain, which could lead to unauthorized access to sensitive data or other security breaches.

As of now, it is essential to check the package repository for any updates or patches that address this vulnerability.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall chime-secrets

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