Malicious Code Injection in lookingan-namakiki68 Package

lookingan-namakiki68 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158581: Malicious code in lookingan-namakiki68 (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-namakiki68 package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's package registry by generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter package metadata, which can lead to unintended consequences for developers relying on it.

Vulnerability Detail

The vulnerability in the lookingan-namakiki68 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, effectively polluting the npm registry. The origin of this vulnerability is linked to automated scripts that aim to inflate developer reputation scores for token rewards, posing significant risks to developers and users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall lookingan-namakiki68

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

Conclusion

The lookingan-namakiki68 package poses a significant security risk due to its malicious code that alters package metadata. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for lookingan-namakiki68 →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign that modifies package metadata to inflate developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability in your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the lookingan-namakiki68 package immediately and audit your dependencies for any other potentially compromised packages.

There are no patches available for the lookingan-namakiki68 package as it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall lookingan-namakiki68

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