Which versions of avvvatars-vue are malicious?

The following npm versions of avvvatars-vue are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate avvvatars-vue if I installed it?

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

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

Yes — avvvatars-vue is associated with the GHSA-fvr9-qhw8-v3w6 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 avvvatars-vue 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 avvvatars-vue (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging avvvatars-vue across your stack and pipelines.

Malicious package

avvvatars-vuenpm

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

MAL-2025-191067

Immediate action

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

npm uninstall avvvatars-vue

What this malware does

The package avvvatars-vue 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.1.2

Indicators of compromise (SHA-256)

e5704fc14aead5570b7b1abc795002ea942c9f791057989143dbe27384b20259

147f35642dddb238d6e235922992164cf8a47925095bc03e185bf2cfa57440aa

9d0177ed2908c06ff8f5fa7cf686ba026f4f225b8c4abe0678cbd28c4962b8fc

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

Campaign

GHSA-fvr9-qhw8-v3w6

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks avvvatars-vue-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