Malicious Code Detected in secure-monkey Package - npm Vulnerability

secure-monkey Updated 26 Feb 2026

Summary

23/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1041: Malicious code in secure-monkey (npm). Affects secure-monkey versions 1.0.0 – 1.1.2. 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 'secure-monkey' package is an npm library designed for various functionalities in JavaScript applications. However, it has been flagged for malicious behavior, specifically in version 1.0.0. This vulnerability poses a significant risk to applications that rely on this package, as it may execute harmful commands that compromise the security of the application and its environment.

Vulnerability Detail

The vulnerability in the 'secure-monkey' package arises from its ability to execute commands associated with malicious behavior. This was identified by the OpenSSF Package Analysis project, which flagged version 1.0.0 as malicious. The ramifications of this vulnerability include potential unauthorized access to sensitive data, execution of harmful scripts, and overall compromise of the application’s integrity. The malicious nature of the package can lead to severe security breaches if not addressed promptly.

How To Fix

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

npm uninstall secure-monkey

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

If immediate updating is not feasible, consider removing the 'secure-monkey' package from your project until a safe version is confirmed. You can do this by running: npm uninstall secure-monkey. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The 'secure-monkey' package has been identified as malicious, particularly in version 1.0.0. It is crucial for developers to update to a safe version to mitigate risks associated with this vulnerability. Regular monitoring and prompt action can help maintain the security of applications relying on open-source packages.

See every vulnerability recorded for secure-monkey →

Share this vulnerability

FAQ

The 'secure-monkey' package is an npm library used in JavaScript applications, but it has been identified as malicious in certain versions.

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

If you cannot update the package, consider uninstalling it temporarily and monitoring your application for any suspicious activity.

Using the vulnerable version can lead to unauthorized access, execution of harmful commands, and potential data breaches.

More information can be found in the OpenSSF Package Analysis report and on the official npm package page.

How To Fix

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

npm uninstall secure-monkey

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