Critical Malicious Code Vulnerability in pkg1511222 (npm)

pkg1511222 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1815: Malicious code in pkg1511222 (npm). Affects pkg1511222 versions 99.99.99. 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

pkg1511222 is an npm package that serves as a utility for developers, providing various functionalities to enhance their applications. However, this package has been flagged for containing malicious code, which poses significant risks to users who integrate it into their projects. The vulnerability allows attackers to exploit the package, potentially leading to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability identified as MAL-2026-1815 originates from malicious code embedded within the pkg1511222 package. This code can execute harmful actions on the user's system, such as stealing sensitive information or compromising application integrity. The affected version is 99.99.99, and users are strongly advised to avoid using this version to mitigate risks.

How To Fix

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

npm uninstall pkg1511222

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, users can remove the pkg1511222 package from their project until a secure version is released. This can be done using the command: npm uninstall pkg1511222. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The pkg1511222 package has been identified with a critical vulnerability due to malicious code. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain security in open-source projects.

See every vulnerability recorded for pkg1511222 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can execute harmful actions on the user's system, potentially leading to data breaches.

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

If you have installed pkg1511222, it is recommended to uninstall the package immediately and check for any updates or patches.

Currently, the affected version is 99.99.99. Users should monitor the package repository for any updates or patches that address this vulnerability.

Ignoring this vulnerability could lead to unauthorized access to sensitive data, application compromise, and significant security risks for your project.

How To Fix

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

npm uninstall pkg1511222

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