Which versions of engineers are malicious?

The following npm versions of engineers are flagged malicious: 0.0.0-0, 0.0.0-1. Treat any of these as compromised.

How do I remediate engineers if I installed it?

Remove engineers from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed engineers — how do I know if it already compromised me?

If engineers was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is engineers part of a known attack campaign?

Yes — engineers is associated with the RLMA-2026-01285 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find engineers across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for engineers (2 malicious versions).

Malicious package

engineersnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

engineers is a confirmed malicious npm package (MAL-2026-1724) that executes malicious code on install (malicious versions 0.0.0-0, 0.0.0-1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in engineers (npm)

MAL-2026-1724

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall engineers

What this malware does

The package engineers was found to contain malicious code.

Malicious versions

2 flagged

0.0.0-00.0.0-1

Indicators of compromise (SHA-256)

175b171497e671834bcd9553cb99344bb71c62f37d894fe4032cbc63c3014e07

50c4ca242458b8c1b2f1bfbcab1d2c3253c39979d43c89a9489f09ca1575356d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for engineers (2 malicious versions).
If you installed it — respond
Remove engineers from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If engineers was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. engineers on npm has been identified as a malicious package (versions 0.0.0-0, 0.0.0-1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01285

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks engineers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database