Malicious Code Injection in intensive_macaw_z3n Package

intensive_macaw_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104313: Malicious code in intensive_macaw_z3n (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 intensive_macaw_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability stems from the package being involved in a token reward campaign that floods the npm registry with malicious packages. It contains scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to reputation inflation for malicious actors and potential security risks for users of the package.

How To Fix

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

npm uninstall intensive_macaw_z3n

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 workaround, you can temporarily avoid using the intensive_macaw_z3n package and monitor your application for any dependencies that may have been affected. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. Here’s how to use Vulert: Visit https://vulert.com/scanner and upload your package-lock.json file to check for any vulnerabilities.

Conclusion

The intensive_macaw_z3n package poses a significant security risk due to its involvement in a malicious campaign that exploits npm's publishing system. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for intensive_macaw_z3n →

Share this vulnerability

FAQ

The intensive_macaw_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.

The malicious code can lead to the pollution of the npm registry, potentially introducing security vulnerabilities into your application and affecting its integrity.

If you have installed the intensive_macaw_z3n package, you should uninstall it immediately and check your project for any other affected dependencies.

You can use Vulert to monitor your project for vulnerabilities by analyzing your package-lock.json file. This tool provides real-time alerts for open-source vulnerabilities.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall intensive_macaw_z3n

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