Which versions of skills-use are malicious?

The following npm versions of skills-use are flagged malicious: 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate skills-use if I installed it?

skills-use 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 skills-use — how do I know if it already compromised me?

If skills-use 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 skills-use part of a known attack campaign?

Yes — skills-use is associated with the GHSA-vqq7-66xf-8cmr 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 skills-use 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 skills-use (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging skills-use across your stack and pipelines.

Malicious package

skills-usenpm

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

MAL-2025-190783

Immediate action

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

npm uninstall skills-use

What this malware does

The package skills-use 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.10.1.2

Indicators of compromise (SHA-256)

25e55ca30592985c5f31158f8bd68d19643e2b48db1cf4578a7da6ae380ed661

f974e3dc3206af78c8a6fd5370b73dc14d8edc1f052caa4992fdca5c5bac45ac

350de9b598c448b204c98af476a625b4a17f62adf252ce9293de3d16240245ba

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

Campaign

GHSA-vqq7-66xf-8cmr

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks skills-use-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