Which versions of ghscan-pkgcheck-test-001 are malicious?

The following npm versions of ghscan-pkgcheck-test-001 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate ghscan-pkgcheck-test-001 if I installed it?

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

If ghscan-pkgcheck-test-001 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.

Is ghscan-pkgcheck-test-001 part of a known attack campaign?

Yes — ghscan-pkgcheck-test-001 is associated with the RLMA-2026-01954 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 ghscan-pkgcheck-test-001 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ghscan-pkgcheck-test-001 (version 0.0.1).

Malicious package

ghscan-pkgcheck-test-001npm

Advisory published Apr 16, 2026Updated Apr 23, 2026

ghscan-pkgcheck-test-001 is a confirmed malicious npm package (MAL-2026-2765) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ghscan-pkgcheck-test-001 (npm)

MAL-2026-2765

Immediate action

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

npm uninstall ghscan-pkgcheck-test-001

What this malware does

The package ghscan-pkgcheck-test-001 was found to contain malicious code.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2ab914ba5f89e6ded686c388ee12190632a30acbb49ff97c7694344797b647e2

867757df0e86dde6839938aaabe7b5c9574bf49dae685032524081e87f8b3435

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01954

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ghscan-pkgcheck-test-001-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