Malicious Code Detected in atmohue Package - Security Alert

atmohue Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15019: Malicious code in atmohue (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 atmohue package is a Node.js library designed for specific functionalities within the npm ecosystem. It is utilized by developers for its unique features, which enhance application performance and user experience. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the atmohue package originates from the inclusion of malicious code that can compromise the integrity of applications using it. This malicious code may lead to unauthorized access, data breaches, or other harmful actions that can affect both developers and end-users. The issue is present in all versions starting from 0, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall atmohue

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 atmohue package from your project until a secure version is released. You can do this by executing the following command: npm uninstall atmohue. This will help mitigate the risks associated with the malicious code.

Conclusion

The atmohue package has been identified as containing malicious code, posing a serious security threat to applications that utilize it. It is crucial for developers to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for atmohue →

Share this vulnerability

FAQ

The atmohue package is a Node.js library used in the npm ecosystem for various functionalities within applications.

The malicious code in atmohue can lead to unauthorized access and data breaches, potentially compromising application security.

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

Check the npm repository for any updates or patches for the atmohue package to address the vulnerability.

As a temporary measure, consider uninstalling the atmohue package from your project to reduce security risks.

How To Fix

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

npm uninstall atmohue

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