Which versions of paddle-internal-scripts are malicious?

Every published version of paddle-internal-scripts on npm is considered malicious. Remove the package entirely.

How do I remediate paddle-internal-scripts if I installed it?

paddle-internal-scripts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed paddle-internal-scripts — how do I know if it already compromised me?

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

Search your lockfiles and build artifacts for paddle-internal-scripts (all published versions).

Malicious package

paddle-internal-scriptsnpm

Advisory published Apr 17, 2026Updated Apr 23, 2026

paddle-internal-scripts is a confirmed malicious npm package (MAL-2026-2829) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in paddle-internal-scripts (npm)

MAL-2026-2829

Immediate action

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

npm uninstall paddle-internal-scripts

What this malware does

Malicious package due to sensitive data exfiltration via obfuscated preinstall script. Few published versions increase suspicion.

The package paddle-internal-scripts was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

eae655788b800d689464263a26d904ccb45fe4aa65b61422a51325008aff3003

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for paddle-internal-scripts (all published versions).
If you installed it — respond
paddle-internal-scripts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If paddle-internal-scripts 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. paddle-internal-scripts on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks paddle-internal-scripts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database