Malicious Code Injection in ferawijaya Package: npm Vulnerability Overview

ferawijaya Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171217: Malicious code in ferawijaya (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ferawijaya package is part of the npm ecosystem, primarily used for JavaScript development. It is often utilized in various applications to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and their projects.

Vulnerability Detail

The vulnerability in the ferawijaya package originates from its association with a malicious campaign designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. This malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry and compromise the integrity of projects relying on this package.

How To Fix

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

npm uninstall ferawijaya

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 remove the ferawijaya package from your project by executing: npm uninstall ferawijaya. This will prevent any malicious code from executing while you assess the situation and look for alternative packages.

Conclusion

The ferawijaya package has been identified as a vector for malicious code that can compromise npm projects. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to protect their applications. Regularly updating dependencies and utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for ferawijaya →

Share this vulnerability

FAQ

The ferawijaya package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall ferawijaya

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