Which versions of pulsar-mocha-saturnology-jupiter are malicious?

Every published version of pulsar-mocha-saturnology-jupiter on npm is considered malicious. Remove the package entirely.

How do I remediate pulsar-mocha-saturnology-jupiter if I installed it?

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

If pulsar-mocha-saturnology-jupiter 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 pulsar-mocha-saturnology-jupiter across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pulsar-mocha-saturnology-jupiter (all published versions).

Malicious package

pulsar-mocha-saturnology-jupiternpm

Advisory published Nov 13, 2025Updated Nov 13, 2025

pulsar-mocha-saturnology-jupiter is a confirmed malicious npm package (MAL-2025-188972) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pulsar-mocha-saturnology-jupiter (npm)

MAL-2025-188972

Immediate action

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

npm uninstall pulsar-mocha-saturnology-jupiter

What this malware does

This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The malicious payload modifies package.json to remove private flags, changes version numbers, generates random Indonesian-themed package names (some variants are also in English), and continuously republishes variants to pollute the npm registry.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

7e9af36bde91252a42ee3406851e9f22162b169e8cd83b2d46b3e2ab72d99eba

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pulsar-mocha-saturnology-jupiter (all published versions).
If you installed it — respond
Remove pulsar-mocha-saturnology-jupiter 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 pulsar-mocha-saturnology-jupiter 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. pulsar-mocha-saturnology-jupiter 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.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pulsar-mocha-saturnology-jupiter-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