What does the rookie-security-test-pkg malware do?

The OpenSSF Package Analysis project identified 'rookie-security-test-pkg' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of rookie-security-test-pkg are malicious?

The following npm versions of rookie-security-test-pkg are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate rookie-security-test-pkg if I installed it?

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

If rookie-security-test-pkg 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 rookie-security-test-pkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rookie-security-test-pkg (version 1.0.0).

Malicious package

rookie-security-test-pkgnpm

Advisory published Jun 1, 2026Updated Jun 1, 2026

rookie-security-test-pkg is a confirmed malicious npm package (MAL-2026-5132) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rookie-security-test-pkg (npm)

MAL-2026-5132

Immediate action

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

npm uninstall rookie-security-test-pkg

What this malware does

The OpenSSF Package Analysis project identified 'rookie-security-test-pkg' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1af47f1485c4c5bd3c6ee3cb7330781c1892ebc8bea1c59b0a0045c49ab8c93d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rookie-security-test-pkg (version 1.0.0).
If you installed it — respond
Remove rookie-security-test-pkg 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 rookie-security-test-pkg 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. rookie-security-test-pkg on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks rookie-security-test-pkg-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