Which versions of vf-oss-template are malicious?

The following npm versions of vf-oss-template are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate vf-oss-template if I installed it?

vf-oss-template 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 vf-oss-template — how do I know if it already compromised me?

If vf-oss-template 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 vf-oss-template part of a known attack campaign?

Yes — vf-oss-template is associated with the RLMA-2025-06524 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 vf-oss-template 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 vf-oss-template (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vf-oss-template across your stack and pipelines.

Malicious package

vf-oss-templatenpm

Malicious code in vf-oss-template (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191447

Immediate action

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

npm uninstall vf-oss-template

What this malware does

The package vf-oss-template was found to contain malicious code.

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

4 flagged

1.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

5aab1429675f85376bd921f9f6c79d7878c53d4c59002a0269af1003fd1b6044

d103d87bdd4b4e74f7f65f5726dc9eac4871a42a7298a619c317e9931c42aa84

3e750fa2c56f959c3fe36251cc187767b9d8ea408ff1842f94bece1be4a5bee4

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

Campaign

RLMA-2025-06524

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vf-oss-template-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