Malicious Code Injection in lookingan-nalako36: A Threat to npm Ecosystem

lookingan-nalako36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158445: Malicious code in lookingan-nalako36 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'lookingan-nalako36' 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 npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in 'lookingan-nalako36' originates from its malicious payload that modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious scripts included in this package are designed to automate these processes, making it difficult for developers to identify and mitigate the threat.

How To Fix

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

npm uninstall lookingan-nalako36

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 monitor your package dependencies for any malicious activity. Consider using tools like Vulert, which allows you to check your application for vulnerabilities without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The 'lookingan-nalako36' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and take immediate action to remove such packages from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for lookingan-nalako36 →

Share this vulnerability

FAQ

'lookingan-nalako36' is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and making it susceptible to further attacks.

You should uninstall the 'lookingan-nalako36' package immediately and review your project's dependencies for any other potentially malicious packages.

Regularly update your dependencies, use trusted packages, and employ tools like Vulert to monitor your project for vulnerabilities.

There is no patch for 'lookingan-nalako36' as it is a malicious package. The best course of action is to uninstall it and ensure your project is secure.

How To Fix

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

npm uninstall lookingan-nalako36

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