Which versions of greet-test are malicious?

The following npm versions of greet-test are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate greet-test if I installed it?

Remove greet-test 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 greet-test — how do I know if it already compromised me?

If greet-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find greet-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for greet-test (2 malicious versions).

Malicious package

greet-testnpm

Advisory published Oct 30, 2025Updated Oct 1, 2026

greet-test is a confirmed malicious npm package (MAL-2025-49225) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in greet-test (npm)

MAL-2025-49225

Immediate action

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

npm uninstall greet-test

What this malware does

The package greet-test was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

b30f8cd06e021bf526fe03bcd0e36719d5cb4afcb10a57f58d28b5ba6f8ff3db

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for greet-test (2 malicious versions).
If you installed it — respond
Remove greet-test 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 greet-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. greet-test on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks greet-test-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

Explore

All malware advisories How O3 detects malware Vulnerability database