Which versions of garfield000 are malicious?

Every published version of garfield000 on npm is considered malicious. Remove the package entirely.

How do I remediate garfield000 if I installed it?

Remove garfield000 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed garfield000 — how do I know if it already compromised me?

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

Yes — garfield000 is associated with the GHSA-377q-vgp4-qxgm 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 garfield000 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 garfield000 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging garfield000 across your stack and pipelines.

Malicious package

garfield000npm

Malicious code in garfield000 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-113

Immediate action

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

npm uninstall garfield000

What this malware does

The package garfield000 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

12e916aed66acb12d51a1fc4b756247f696863776624c776a3b38e84acbdc6fc

be6ac9b34a6d30c7ec66b0526fba72fda30519c2b623116e96663d5f3ec73d42

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for garfield000 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging garfield000 across your stack and pipelines.
If you installed it — respond
Remove garfield000 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If garfield000 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 garfield000 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. garfield000 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-377q-vgp4-qxgm

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks garfield000-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring