Malicious Code Injection in lookingan-nalako52 Package

lookingan-nalako52 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158463: Malicious code in lookingan-nalako52 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The lookingan-nalako52 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 distribute malicious packages that inflate developer reputation scores through automated scripts. The presence of such malicious code poses a significant risk to developers and their projects.

Vulnerability Detail

The vulnerability in the lookingan-nalako52 package originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The malicious payload can affect developers by inflating their reputation scores through illegitimate means, leading to a loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall lookingan-nalako52

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 remove the lookingan-nalako52 package from your project by executing the command: 'npm uninstall lookingan-nalako52'. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The lookingan-nalako52 package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications. Regularly updating packages and utilizing monitoring tools like Vulert can help mitigate risks associated with open-source vulnerabilities.

See every vulnerability recorded for lookingan-nalako52 →

Share this vulnerability

FAQ

The lookingan-nalako52 package is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated scripts.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and reputation.

If you have installed the lookingan-nalako52 package, it is recommended to uninstall it immediately and check for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json file for 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 any signup.

How To Fix

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

npm uninstall lookingan-nalako52

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