What does the pa-marked-internal malware do?

The package pa-marked-internal was found to contain malicious code. The OpenSSF Package Analysis project identified 'pa-marked-internal' @ 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 pa-marked-internal are malicious?

The following npm versions of pa-marked-internal are flagged malicious: 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate pa-marked-internal if I installed it?

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

If pa-marked-internal 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 pa-marked-internal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pa-marked-internal (2 malicious versions).

Malicious package

pa-marked-internalnpm

Advisory published Apr 19, 2026Updated Apr 23, 2026

pa-marked-internal is a confirmed malicious npm package (MAL-2026-2928) that executes malicious code on install (malicious versions 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pa-marked-internal (npm)

MAL-2026-2928

Immediate action

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

npm uninstall pa-marked-internal

What this malware does

The package pa-marked-internal was found to contain malicious code.

The OpenSSF Package Analysis project identified 'pa-marked-internal' @ 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

2 flagged

1.0.11.0.3

Indicators of compromise (SHA-256)

1d618c2f983bf33eb7a449adf96ad491b51b23573e34f3ccdf8ed960147ed70e

aac4ede7ac259c3abd6ce42f4c79498f8307ce22b67f5c4c5aa10f19142c570c

aa7ec58688a86a684649482df31ee2d5ded2b22d648049ab9a2d6ba93bb912b0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pa-marked-internal (2 malicious versions).
If you installed it — respond
Remove pa-marked-internal 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 pa-marked-internal 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. pa-marked-internal on npm has been identified as a malicious package (versions 1.0.1, 1.0.3 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 pa-marked-internal-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