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

manurung-poke44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160065: Malicious code in manurung-poke44 (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

manurung-poke44 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary functionality of this package is to generate and publish derivative packages, but it has been compromised to include malicious scripts that can alter package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in manurung-poke44 stems from its inclusion in a campaign that utilizes autopublish scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and create random package names, leading to the pollution of the npm registry. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the integrity of the npm ecosystem, affecting developers and users relying on legitimate packages.

How To Fix

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

npm uninstall manurung-poke44

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, you can avoid using the manurung-poke44 package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.

Conclusion

The discovery of malicious code in the manurung-poke44 package highlights the importance of vigilance in managing npm dependencies. By promptly removing affected packages and utilizing monitoring tools like Vulert, developers can safeguard their projects against potential threats.

See every vulnerability recorded for manurung-poke44 →

Share this vulnerability

FAQ

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

The vulnerability can lead to unauthorized changes in your package metadata, potentially compromising your project's integrity and security.

You should uninstall the manurung-poke44 package immediately and review your other dependencies for any potential vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring 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 manurung-poke44

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