Malicious Code Injection in lookingan-nakomi33 Package - npm Vulnerability

lookingan-nakomi33 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158392: Malicious code in lookingan-nakomi33 (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-nakomi33 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 linked to malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to the presence of scripts that generate and publish derivative packages with altered metadata, leading to potential security risks.

Vulnerability Detail

The vulnerability in the lookingan-nakomi33 package originates from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, making it difficult for developers to maintain the integrity of their projects. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security breaches in their applications.

How To Fix

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

npm uninstall lookingan-nakomi33

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 avoid using the lookingan-nakomi33 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The lookingan-nakomi33 package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for lookingan-nakomi33 →

Share this vulnerability

FAQ

The lookingan-nakomi33 package is a JavaScript package in the npm ecosystem that is linked to a malicious campaign aimed at inflating developer reputation scores.

The malicious code modifies your package.json file, potentially leading to the installation of compromised packages and security vulnerabilities in your application.

You should uninstall the lookingan-nakomi33 package immediately using the command npm uninstall lookingan-nakomi33.

Yes, tools like Vulert can help monitor your project's dependencies for vulnerabilities in real-time without requiring access to the code.

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

How To Fix

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

npm uninstall lookingan-nakomi33

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