Malicious Code Detected in adv-web-publishing-assignment-2 Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14120: Malicious code in adv-web-publishing-assignment-2 (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 adv-web-publishing-assignment-2 package is an npm module designed for web publishing assignments. It typically includes functionalities for managing web content and assignments efficiently. However, this package has been identified to contain malicious code, which poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the adv-web-publishing-assignment-2 package. This code can potentially compromise user data, allow unauthorized access, or execute harmful actions within the user's environment. The malicious nature of this code can lead to severe ramifications, including data breaches and system integrity issues.

How To Fix

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

npm uninstall adv-web-publishing-assignment-2

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 packages that provide similar functionalities without the associated risks. Always ensure to review the package's reputation and security status before integrating it into your project.

Conclusion

The adv-web-publishing-assignment-2 package has been flagged for containing malicious code, posing significant security risks. Users are advised to uninstall the package and monitor for updates or alternatives to ensure the safety of their applications.

See every vulnerability recorded for adv-web-publishing-assignment-2 →

Share this vulnerability

FAQ

It is an npm module used for managing web publishing assignments, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

The risks include data breaches, unauthorized access, and potential harm to system integrity due to the malicious code.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

Consider using alternative packages that provide similar functionalities without the associated risks while you plan for a complete removal.

How To Fix

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

npm uninstall adv-web-publishing-assignment-2

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