Malicious Code Exploit in lookingan-namakiki80 Package: A Threat to npm Users

lookingan-namakiki80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158595: Malicious code in lookingan-namakiki80 (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-namakiki80 package is part of a broader campaign targeting npm users, specifically designed to manipulate the npm registry. It is associated with the tea.xyz token reward initiative, which incentivizes developers to publish numerous packages. This package, like others in the campaign, is engineered to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the lookingan-namakiki80 package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches and reputational damage.

How To Fix

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

npm uninstall lookingan-namakiki80

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-namakiki80 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The lookingan-namakiki80 package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for lookingan-namakiki80 →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that automates the publication of derivative packages.

The vulnerability can lead to the installation of malicious code, compromising your project's security and integrity.

You should remove the lookingan-namakiki80 package from your project immediately and monitor your dependencies for any malicious activity.

Yes, regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and only install packages from trusted sources.

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

How To Fix

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

npm uninstall lookingan-namakiki80

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