Which versions of standalone-apps are malicious?

The following npm versions of standalone-apps are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate standalone-apps if I installed it?

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

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

Yes — standalone-apps is associated with the GHSA-9whf-2j26-8mhh 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 standalone-apps across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for standalone-apps (version 1.0.1).

Malicious package

standalone-appsnpm

Advisory published Apr 25, 2026Updated May 25, 2026

standalone-apps is a confirmed malicious npm package (MAL-2026-3037) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in standalone-apps (npm)

MAL-2026-3037

Immediate action

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

npm uninstall standalone-apps

What this malware does

The package standalone-apps 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.

The OpenSSF Package Analysis project identified 'standalone-apps' @ 1.0.1 (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.1

Indicators of compromise (SHA-256)

3fb70e7334d6b608e0f9f3f3a8417390f47fa5b57d497dced9fc924b20181c06

22e6c4c826820874f1cb33ef8066313b4714652d4e70a69a343595a62f57e038

16f035cde2e3e7ff7907dcbc9f16e05fca1c373ea51adbd2d5a2b484532ec88d

Detection & response playbook

Malicious package

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

Campaign

GHSA-9whf-2j26-8mhh

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks standalone-apps-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