Malicious Code Vulnerability in Engineers Package (npm)

engineers Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1724: Malicious code in engineers (npm). Affects engineers versions 0.0.0-0 – 0.0.0-1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'engineers' package is a Node.js library available via npm, designed to assist developers with various engineering-related tasks. It is widely used in applications that require engineering computations and data processing. However, this package has been identified as containing malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the 'engineers' package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or system manipulation. The affected versions are '0.0.0-0' and '0.0.0-1', which may allow attackers to exploit the vulnerability and execute harmful actions within the application environment.

How To Fix

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

npm uninstall engineers

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 an immediate workaround, consider removing the 'engineers' package from your project until a secure version is released. You can do this by running the command: 'npm uninstall engineers'. Additionally, review your project's dependencies for any other potentially vulnerable packages.

Conclusion

The 'engineers' package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is essential to update or remove the package to mitigate potential security threats. Utilizing tools like Vulert can aid in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for engineers →

Share this vulnerability

FAQ

The 'engineers' package is a Node.js library that helps developers perform engineering-related tasks and computations.

You can use Vulert to monitor and alert for open-source vulnerabilities. By checking your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

If immediate updates are not possible, consider removing the package and reviewing your dependencies for other vulnerabilities.

Detailed information about this vulnerability can be found on the GitHub repository for malicious packages and the npm package page.

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

How To Fix

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

npm uninstall engineers

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