Which versions of scouthus921 are malicious?

The following npm versions of scouthus921 are flagged malicious: 1.20.22. Treat any of these as compromised.

How do I remediate scouthus921 if I installed it?

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

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

Yes — scouthus921 is associated with the GHSA-vmx4-r7wj-hfxr, RLMA-2025-05503, RLUA-2025-05942 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 scouthus921 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 scouthus921 (version 1.20.22). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scouthus921 across your stack and pipelines.

Malicious package

scouthus921npm

scouthus921 is a confirmed malicious npm package (MAL-2025-48415) that executes malicious code on install (malicious version 1.20.22). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in scouthus921 (npm)

MAL-2025-48415

Immediate action

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

npm uninstall scouthus921

What this malware does

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

1 flagged

1.20.22

Indicators of compromise (SHA-256)

a2e34a89c347498d30a051b684807d976b3a5384c3f333621359e5a0fc90c8ff

e14fc60bdb16b556fcc3f64bea12633959c03b6edb8bc3f543ba9256cad17091

400967ef962962781e784eee2c926f7d3f02f54d4d6b177f920a84717e00197b

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

Campaign

GHSA-vmx4-r7wj-hfxrRLMA-2025-05503RLUA-2025-05942

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks scouthus921-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