Which versions of jaetut-varit-test are malicious?

The following npm versions of jaetut-varit-test are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate jaetut-varit-test if I installed it?

jaetut-varit-test 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 jaetut-varit-test — how do I know if it already compromised me?

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

Yes — jaetut-varit-test is associated with the GHSA-m22g-prpc-hmcg 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 jaetut-varit-test 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 jaetut-varit-test (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jaetut-varit-test across your stack and pipelines.

Malicious package

jaetut-varit-testnpm

Malicious code in jaetut-varit-test (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191112

Immediate action

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

npm uninstall jaetut-varit-test

What this malware does

The package jaetut-varit-test 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

1 flagged

1.0.2

Indicators of compromise (SHA-256)

3dfe3cdbc6f0953604558a82547de507221fe01163b681a46aa6fc48fb9c3954

c4d9e7b0e6bfd2cccd7c0acfccfef9c63d786522d5bc2125163b084062ef17fb

e85e1a4defa66ffea068e9c6df340133d21686f29ad138d73976ff88d60ef368

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

Campaign

GHSA-m22g-prpc-hmcg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jaetut-varit-test-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