Malicious Code Detected in apwimgr Package - Immediate Action Required

apwimgr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14754: Malicious code in apwimgr (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 apwimgr package is a Node.js library designed for managing application packages. It provides functionalities that allow developers to streamline their package management processes. However, it has been identified that this package contains malicious code, which poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the apwimgr package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and has been flagged for its potential to exploit vulnerabilities in the ecosystem.

How To Fix

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

npm uninstall apwimgr

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, consider using alternative package management solutions or libraries that do not exhibit this vulnerability. Additionally, you can monitor your project for any dependencies that may be affected by similar vulnerabilities.

Conclusion

The discovery of malicious code in the apwimgr package highlights the importance of maintaining secure coding practices and regularly auditing dependencies. Immediate action is required to mitigate risks associated with this vulnerability, including removing the affected package and monitoring for updates.

See every vulnerability recorded for apwimgr →

Share this vulnerability

FAQ

The apwimgr package is a Node.js library used for managing application packages, providing various functionalities to streamline package management.

The malicious code was identified through security audits and reports from tools like Amazon Inspector, which flagged the package for containing harmful code.

Using the apwimgr package can lead to unauthorized access, data breaches, and potential exploitation of your application, compromising its integrity and security.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup or installation.

How To Fix

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

npm uninstall apwimgr

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