Which versions of unescaped are malicious?

The following npm versions of unescaped are flagged malicious: 10.0.1. Treat any of these as compromised.

How do I remediate unescaped if I installed it?

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

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

Yes — unescaped is associated with the GHSA-9v63-3x67-86gp 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 unescaped 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 unescaped (version 10.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unescaped across your stack and pipelines.

Malicious package

unescapednpm

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

Malicious code in unescaped (npm)

MAL-2025-41447

Immediate action

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

npm uninstall unescaped

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.

The OpenSSF Package Analysis project identified 'unescaped' @ 10.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

10.0.1

Indicators of compromise (SHA-256)

d0a9acd6b060c5e19eb422ebfb122c3a5c8a33430b4bd4967b46689cd8de13e7

d0ffb644411c73e269e09ef4f2dafc3360dfe3f2fd987506c73ea801aa12bdec

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

Campaign

GHSA-9v63-3x67-86gp

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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