Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @mipta19 published 153 malicious packages. See the full campaign →
Malicious package

@mipta19/s-core-1rnpm

Advisory published Updated

@mipta19/s-core-1r is a confirmed malicious npm package (MAL-2025-150430) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mipta19/s-core-1r (npm)

MAL-2025-150430
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mipta19/s-core-1r

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)

405b2834b1267844ff7ac46ce6458822a569c0ed9203102a3b2d3705c4f9107e

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @mipta19/s-core-1r (all published versions).

  2. If you installed it — respond

    @mipta19/s-core-1r 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.

  3. Did it already run?

    If @mipta19/s-core-1r 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. @mipta19/s-core-1r 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 @mipta19/s-core-1r-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
@mipta19/s-core-1r (npm) malicious package — MAL-2025-150430 | O3 Security