Which versions of @varsityvibe/validation-schemas are malicious?

The following npm versions of @varsityvibe/validation-schemas are flagged malicious: 0.6.7, 0.6.8. Treat any of these as compromised.

How do I remediate @varsityvibe/validation-schemas if I installed it?

@varsityvibe/validation-schemas 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 @varsityvibe/validation-schemas — how do I know if it already compromised me?

If @varsityvibe/validation-schemas 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 @varsityvibe/validation-schemas part of a known attack campaign?

Yes — @varsityvibe/validation-schemas is associated with the GHSA-jqcj-cc9g-j67v 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 @varsityvibe/validation-schemas 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 @varsityvibe/validation-schemas (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @varsityvibe/validation-schemas across your stack and pipelines.

Malicious package

@varsityvibe/validation-schemasnpm

Malicious code in @varsityvibe/validation-schemas (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191062

Immediate action

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

npm uninstall @varsityvibe/validation-schemas

What this malware does

The package @varsityvibe/validation-schemas 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.6.70.6.8

Indicators of compromise (SHA-256)

54f7b89e035610beb9ac9175b9c7802afdb03338e6076a5126cef14725b77b47

1bb29d59e29a1facb82bd1c50b65195a696f8bb2900cf7dc43178a74010415e9

cbd2bb2effb1b3935deef38346c305be9651765d2e15c4256943b343b2a3c6f3

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

Campaign

GHSA-jqcj-cc9g-j67v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @varsityvibe/validation-schemas-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