Which versions of @ifelsedeveloper/protocol-contracts-svm-idl are malicious?

The following npm versions of @ifelsedeveloper/protocol-contracts-svm-idl are flagged malicious: 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate @ifelsedeveloper/protocol-contracts-svm-idl if I installed it?

@ifelsedeveloper/protocol-contracts-svm-idl 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 @ifelsedeveloper/protocol-contracts-svm-idl — how do I know if it already compromised me?

If @ifelsedeveloper/protocol-contracts-svm-idl 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 @ifelsedeveloper/protocol-contracts-svm-idl part of a known attack campaign?

Yes — @ifelsedeveloper/protocol-contracts-svm-idl is associated with the GHSA-xgj5-84xr-63rm 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 @ifelsedeveloper/protocol-contracts-svm-idl 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 @ifelsedeveloper/protocol-contracts-svm-idl (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ifelsedeveloper/protocol-contracts-svm-idl across your stack and pipelines.

Malicious package

@ifelsedeveloper/protocol-contracts-svm-idlnpm

Malicious code in @ifelsedeveloper/protocol-contracts-svm-idl (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191235

Immediate action

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

npm uninstall @ifelsedeveloper/protocol-contracts-svm-idl

What this malware does

The package @ifelsedeveloper/protocol-contracts-svm-idl 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

0.1.20.1.3

Indicators of compromise (SHA-256)

01f36e2d64aff8cffe6ef41587baca6abe0e1839fef0925a7e72c5b3c8f9ac66

f61e07701985e8f99d578845d6823da07c87bf03efc6afae27e6282a890520ce

dd130cc8248982ebd1e7e043ae67c7d32e9c0d7024c47f51d5af0e9fa1c12c29

0ebad94575bfb2cd8fa2b2a983de3033efaa17be2302b268c8c285d4de8ce9b0

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 @ifelsedeveloper/protocol-contracts-svm-idl (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ifelsedeveloper/protocol-contracts-svm-idl across your stack and pipelines.
If you installed it — respond
@ifelsedeveloper/protocol-contracts-svm-idl 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 @ifelsedeveloper/protocol-contracts-svm-idl 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 @ifelsedeveloper/protocol-contracts-svm-idl 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. @ifelsedeveloper/protocol-contracts-svm-idl on npm has been identified as a malicious package (versions 0.1.2, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xgj5-84xr-63rm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ifelsedeveloper/protocol-contracts-svm-idl-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