Malicious Code Injection in lookingan-nakomi37 Package

lookingan-nakomi37 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158396: Malicious code in lookingan-nakomi37 (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 lookingan-nakomi37 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate the generation and publication of derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the lookingan-nakomi37 package. This code is designed to automatically modify the package.json file by removing private flags and altering version numbers. Additionally, it generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to reputation inflation and compromise the integrity of their projects.

How To Fix

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

npm uninstall lookingan-nakomi37

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, avoid using the lookingan-nakomi37 package and consider using alternative packages that provide similar functionality without the associated risks. Always review package dependencies and their sources before installation.

Conclusion

The lookingan-nakomi37 package poses a significant security risk due to its embedded malicious code. It is crucial for developers to be aware of such vulnerabilities and take immediate action to remove affected packages from their projects. Utilizing tools like Vulert can help in monitoring and alerting for open-source vulnerabilities effectively.

See every vulnerability recorded for lookingan-nakomi37 →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The malicious code modifies your package.json file, potentially compromising your project's integrity and security.

You should uninstall the lookingan-nakomi37 package immediately and check for any dependencies that may be affected.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall lookingan-nakomi37

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