Malicious Code Injection in nasrul-poke36: A Threat to npm Ecosystem

nasrul-poke36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161925: Malicious code in nasrul-poke36 (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 nasrul-poke36 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 flood the npm registry with malicious packages. The primary function of such packages is to generate and publish derivative packages automatically, often leading to reputation inflation for developers involved in the tea protocol token rewards.

Vulnerability Detail

The nasrul-poke36 package contains malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall nasrul-poke36

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 the nasrul-poke36 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies for any malicious packages using tools like Vulert, which can monitor your package-lock.json for vulnerabilities.

Conclusion

The nasrul-poke36 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with unwanted variants. It is crucial for developers to remove this package and monitor their dependencies to ensure the security of their applications.

See every vulnerability recorded for nasrul-poke36 →

Share this vulnerability

FAQ

nasrul-poke36 is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the introduction of unwanted packages into your project.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should uninstall the nasrul-poke36 package immediately using the command npm uninstall nasrul-poke36 and audit your dependencies for any other malicious packages.

Regularly audit your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time, helping you maintain a secure application.

How To Fix

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

npm uninstall nasrul-poke36

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