Malicious Code Injection in manurung-poke65: A Threat to npm Users

manurung-poke65 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160088: Malicious code in manurung-poke65 (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 package 'manurung-poke65' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'manurung-poke65' stems 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 the ecosystem. The malicious payload can affect developers by misleading them into using compromised packages, which may contain harmful code.

How To Fix

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

npm uninstall manurung-poke65

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 measure, avoid using 'manurung-poke65' and any packages that may have been published as part of this malicious campaign. Monitor your project's dependencies and consider using tools like Vulert to identify vulnerabilities in your package-lock.json file. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.

Conclusion

The 'manurung-poke65' package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is essential to remove this package and monitor your dependencies to maintain the security of your projects. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your software.

See every vulnerability recorded for manurung-poke65 →

Share this vulnerability

FAQ

'manurung-poke65' is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall manurung-poke65' and review your other dependencies for potential vulnerabilities.

Regularly update your dependencies, monitor your package-lock.json file for vulnerabilities, and use tools like Vulert to receive real-time alerts.

You can find detailed information about this vulnerability in the Open Source Vulnerability database or by visiting the Vulert website.

How To Fix

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

npm uninstall manurung-poke65

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