Which versions of objectidencryptor are malicious?

The following npm versions of objectidencryptor are flagged malicious: 1.0.5, 1.0.6, 1.0.7. Treat any of these as compromised.

How do I remediate objectidencryptor if I installed it?

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

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

Yes — objectidencryptor is associated with the GHSA-cmrf-hfwx-8f7v, RLMA-2025-05463, RLUA-2025-05898 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 objectidencryptor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for objectidencryptor (3 malicious versions).

Malicious package

objectidencryptornpm

Advisory published Oct 7, 2025Updated Dec 2, 2025

objectidencryptor is a confirmed malicious npm package (MAL-2025-47980) that executes malicious code on install (malicious versions 1.0.5, 1.0.6, 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in objectidencryptor (npm)

MAL-2025-47980

Immediate action

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

npm uninstall objectidencryptor

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

1.0.51.0.61.0.7

Indicators of compromise (SHA-256)

a56edf53649a4f75908a2ae90590fb378924470884be87f373662bce9eab61e8

2d1137da298b5d41e9389b0b4bf1cc35c9a6aa61f0c3f0b78cb100f13bc835de

eed9f56585e142a2a7c8fe77310b35358bd28f6ad97c24a614074e2438725eb0

Detection & response playbook

Malicious package

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

Campaign

GHSA-cmrf-hfwx-8f7vRLMA-2025-05463RLUA-2025-05898

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks objectidencryptor-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