Which versions of @everreal/validate-esmoduleinterop-imports are malicious?

The following npm versions of @everreal/validate-esmoduleinterop-imports are flagged malicious: 1.4.4, 1.4.5. Treat any of these as compromised.

How do I remediate @everreal/validate-esmoduleinterop-imports if I installed it?

@everreal/validate-esmoduleinterop-imports 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 @everreal/validate-esmoduleinterop-imports — how do I know if it already compromised me?

If @everreal/validate-esmoduleinterop-imports 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 @everreal/validate-esmoduleinterop-imports part of a known attack campaign?

Yes — @everreal/validate-esmoduleinterop-imports is associated with the GHSA-v335-px5m-mp9p 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 @everreal/validate-esmoduleinterop-imports 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 @everreal/validate-esmoduleinterop-imports (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @everreal/validate-esmoduleinterop-imports across your stack and pipelines.

Malicious package

@everreal/validate-esmoduleinterop-importsnpm

Malicious code in @everreal/validate-esmoduleinterop-imports (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191216

Immediate action

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

npm uninstall @everreal/validate-esmoduleinterop-imports

What this malware does

The package @everreal/validate-esmoduleinterop-imports 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.4.41.4.5

Indicators of compromise (SHA-256)

19b66a83131d2a96b0a125da4513334f08d1b2149f048c2ea5de13e225bdfd25

70d6698d2ca5930dd43c46c56df79fbb54ff103af79c144f852586d11ed66fe5

0937ec89b2f415695a49aadd01e4560297a804f5c7598e613d516516babbb9d5

dab8b8345156c4c77c99622cb83f321f5904503094e6d54a19585d087a7849a6

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

Campaign

GHSA-v335-px5m-mp9p

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @everreal/validate-esmoduleinterop-imports-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