Malicious Code Injection in lookingan-nakomi36 Package: A Threat to npm Ecosystem

lookingan-nakomi36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158395: Malicious code in lookingan-nakomi36 (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 lookingan-nakomi36 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous variants with randomized names.

Vulnerability Detail

The vulnerability in the lookingan-nakomi36 package originates from its involvement in the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This malicious behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. Developers using this package may unknowingly contribute to the proliferation of malicious packages, which can lead to security risks and loss of trust in the npm registry.

How To Fix

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

npm uninstall lookingan-nakomi36

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, you can avoid using the lookingan-nakomi36 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json and regularly audit your dependencies.

Conclusion

The lookingan-nakomi36 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to protect their projects. By removing the affected package and utilizing monitoring tools like Vulert, developers can mitigate risks and maintain the integrity of their applications.

See every vulnerability recorded for lookingan-nakomi36 →

Share this vulnerability

FAQ

The lookingan-nakomi36 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.

You should remove the lookingan-nakomi36 package from your project immediately and monitor your dependencies for any unauthorized changes.

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

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in your projects.

How To Fix

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

npm uninstall lookingan-nakomi36

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