Malicious Code Detected in atomised-service Package

atomised-service Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15025: Malicious code in atomised-service (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The atomised-service package is an npm library designed to facilitate various service-related functionalities in JavaScript applications. It is commonly used for managing service interactions and enhancing application performance. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the atomised-service package. This code can potentially compromise the security of applications that utilize the package, leading to unauthorized access, data breaches, or other harmful consequences. The malicious code was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall atomised-service

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 measure, users can remove the atomised-service package from their project until a secure version is released. This can be done using the following command: npm uninstall atomised-service. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the atomised-service package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to secure their applications by updating or removing the affected package. Utilizing tools like Vulert can aid in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for atomised-service →

Share this vulnerability

FAQ

atomised-service is an npm library used for managing service interactions in JavaScript applications.

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in open-source packages. Visit Vulert Scanner to use the Vulert playground.

If immediate updates are not possible, consider uninstalling the package and using alternative libraries until a secure version is released.

Utilize tools like Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall atomised-service

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