Malicious Code Injection in lookingan-nakomi34 Package - npm Vulnerability

lookingan-nakomi34 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158393: Malicious code in lookingan-nakomi34 (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-nakomi34 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 serve as a tool for developers, 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-nakomi34 package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The intent behind this malicious behavior is to inflate developer reputation scores for token rewards, leading to the continuous republishing of these compromised packages, which pollutes the npm registry and poses significant risks to developers who unknowingly use these packages.

How To Fix

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

npm uninstall lookingan-nakomi34

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-nakomi34 package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The lookingan-nakomi34 package has been identified as a source of malicious code that can compromise the integrity of npm projects. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.

See every vulnerability recorded for lookingan-nakomi34 →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata.

Using this package can lead to the pollution of your project's dependencies and potentially expose your application to further security risks.

You should uninstall the package immediately using npm uninstall lookingan-nakomi34 and check your project for any other compromised packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall lookingan-nakomi34

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