What does the xpna-context malware do?

The package xpna-context was found to contain malicious code. The OpenSSF Package Analysis project identified 'xpna-context' @ 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.

Which versions of xpna-context are malicious?

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

How do I remediate xpna-context if I installed it?

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

If xpna-context 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 xpna-context across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xpna-context (version 1.0.1).

Malicious package

xpna-contextnpm

Advisory published Mar 27, 2026Updated Mar 31, 2026

xpna-context is a confirmed malicious npm package (MAL-2026-2257) 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 xpna-context (npm)

MAL-2026-2257

Immediate action

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

npm uninstall xpna-context

What this malware does

The package xpna-context was found to contain malicious code.

The OpenSSF Package Analysis project identified 'xpna-context' @ 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)

6cc170474d756b38d5b918706ce87f0930a4e85fb0e94f66f43fd28d70cb4897

678a96ef06b05d2ab867c1eea4dbed1cfc69f99cb4904e02c48736df0da7695e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for xpna-context (version 1.0.1).
If you installed it — respond
Remove xpna-context 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 xpna-context 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. xpna-context 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.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks xpna-context-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