Malicious Code Vulnerability in atomic_lion_0xrequest Package

atomic_lion_0xrequest Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99650: Malicious code in atomic_lion_0xrequest (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 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 atomic_lion_0xrequest package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package specifically is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability originates from the package being part of the tea.xyz token reward campaign, which utilizes malicious scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in compromised developer environments and potential security risks for applications relying on this package.

How To Fix

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

npm uninstall atomic_lion_0xrequest

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 workaround, you can temporarily avoid using the atomic_lion_0xrequest package by removing it from your dependencies. If you need similar functionality, consider using alternative packages that are verified and free from malicious code.

Conclusion

The atomic_lion_0xrequest package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for atomic_lion_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

You should remove the atomic_lion_0xrequest package from your project and monitor for any updates or patches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall atomic_lion_0xrequest

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