Which versions of bind-error are malicious?

The following npm versions of bind-error are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate bind-error if I installed it?

Remove bind-error 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 bind-error — how do I know if it already compromised me?

If bind-error 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 bind-error part of a known attack campaign?

Yes — bind-error is associated with the RLMA-2025-04463, RLUA-2025-05692 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 bind-error across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bind-error (version 1.0.0).

Malicious package

bind-errornpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

bind-error is a confirmed malicious npm package (MAL-2025-41536) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bind-error (npm)

MAL-2025-41536

Immediate action

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

npm uninstall bind-error

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e0068ba7edd06eff970604676f6bb45d4c406bc0287279689e00755ae415bc2e

c6791c0c2765c45b19872242c38e89f2cd854edeac43e9fc44937c287fc34b16

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bind-error (version 1.0.0).
If you installed it — respond
Remove bind-error 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 bind-error 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. bind-error on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04463RLUA-2025-05692

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks bind-error-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