What does the current-context-urn malware do?

The package current-context-urn was found to contain malicious code. The OpenSSF Package Analysis project identified 'current-context-urn' @ 99.10.9 (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 current-context-urn are malicious?

The following npm versions of current-context-urn are flagged malicious: 99.10.9. Treat any of these as compromised.

How do I remediate current-context-urn if I installed it?

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

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

Search your lockfiles and build artifacts for current-context-urn (version 99.10.9).

Malicious package

current-context-urnnpm

Advisory published Mar 27, 2026Updated Mar 31, 2026

current-context-urn is a confirmed malicious npm package (MAL-2026-2258) that executes malicious code on install (malicious version 99.10.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in current-context-urn (npm)

MAL-2026-2258

Immediate action

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

npm uninstall current-context-urn

What this malware does

The package current-context-urn was found to contain malicious code.

The OpenSSF Package Analysis project identified 'current-context-urn' @ 99.10.9 (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

99.10.9

Indicators of compromise (SHA-256)

eb5101c16c1139b882751b140bc4ee3b014d98485f2d05febed67ceb6808401b

4a89385538c4df75cf7f40207e1ccdf6501459d80e8c9a0580955e9422d7c3a4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for current-context-urn (version 99.10.9).
If you installed it — respond
Remove current-context-urn 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 current-context-urn 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. current-context-urn on npm has been identified as a malicious package (version 99.10.9 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 current-context-urn-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