Malicious Code Vulnerability in Snort Security Tool - npm Package

snort-security-tool Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1851: Malicious code in snort-security-tool (npm). Affects snort-security-tool versions 1.0.1 – 1.0.6. 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 Snort Security Tool is an npm package designed for network intrusion detection and prevention. It provides users with the ability to monitor network traffic and identify potential threats. However, recent findings have revealed that certain versions of this package contain malicious code, posing significant security risks to users who rely on it for safeguarding their networks.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the Snort Security Tool package. This code can potentially compromise the integrity of systems using the package, leading to unauthorized access, data breaches, or further exploitation of the affected systems. The malicious code was identified in versions 1.0.1 through 1.0.6, and its origin is linked to a malicious package upload, which was subsequently flagged by security researchers.

How To Fix

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

npm uninstall snort-security-tool

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 affected package from their project by executing 'npm uninstall snort-security-tool' until a secure version is confirmed. Alternatively, consider using a different security tool that does not have known vulnerabilities.

Conclusion

The Snort Security Tool npm package has been found to contain malicious code in several of its versions, posing a serious risk to users. It is crucial to update to a secure version or consider alternative solutions to mitigate potential threats. Regular monitoring with tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for snort-security-tool →

Share this vulnerability

FAQ

Versions 1.0.1 to 1.0.6 of the Snort Security Tool package are affected by this vulnerability.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If immediate updates are not possible, consider uninstalling the package or using an alternative security tool until a secure version is available.

The vulnerability was identified by ReversingLabs, a security research organization that specializes in analyzing malicious software.

Using the affected package can lead to unauthorized access to your systems, data breaches, and further exploitation by malicious actors.

How To Fix

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

npm uninstall snort-security-tool

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