Which versions of compare-obj are malicious?

The following npm versions of compare-obj are flagged malicious: 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate compare-obj if I installed it?

compare-obj is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed compare-obj — how do I know if it already compromised me?

If compare-obj was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is compare-obj part of a known attack campaign?

Yes — compare-obj is associated with the GHSA-fmgq-4crf-7q98 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 compare-obj across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for compare-obj (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging compare-obj across your stack and pipelines.

Malicious package

compare-objnpm

Malicious code in compare-obj (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190950

Immediate action

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

npm uninstall compare-obj

What this malware does

The package compare-obj was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.1.11.1.2

Indicators of compromise (SHA-256)

3a7310cc13d858af4c2dfc25ec5d42cf6aa52b00dd7fc28ba0ee069a68e7551b

1892ab55a1dcdd44c7f030aef1ae76a865ffffe4b7a0d4a0492696c149db2e4d

0fd6d308339159c38ff213bb81173019906fedf3d4f4acdd5747a7a1b84198c8

a58185cb08a94a7c3c42330c2f085a0722f735a633146531ee084acd89eb8799

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for compare-obj (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging compare-obj across your stack and pipelines.
If you installed it — respond
compare-obj is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If compare-obj was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks compare-obj before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-fmgq-4crf-7q98

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks compare-obj-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring