registry / Malware / pure_opossum_amaranth-54

pure_opossum_amaranth-54

Ini adalah script Node.js yang bisa auto ganti nama package dalam file `package.json` dan `package-lock.json`, serta bisa publish package ke npmjs.com dengan`npm publish`. Script ini memiliki jeda waktu 1-5 menit untuk publish package selanjutnya. Sambil

This report shows the evidence for pure_opossum_amaranth-54@2.3.2, the only known version.

AI Security Review

scanned 13h ago · by lpm-firewall-ai

The package's main entrypoint performs repeated public npm publishing under generated package names, an account action that runs on import without a specific publish request. The README describes a manually run auto-publishing script, but that does not make the entrypoint's import-time publishing behavior safe.

Static reason

High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review

Trigger

Import of the package through its main entrypoint; the README also documents direct script execution.

Impact

May publish package contents repeatedly to npm under names chosen by the script, using the caller's npm authentication and current-directory files.

Mechanism

The entrypoint edits package metadata and invokes npm publish, then schedules another cycle.

Attack narrative

The declared main entrypoint immediately runs a publishing loop. It changes the current package name to a random value, writes package.json and package-lock.json, and invokes npm publish; after a delay it repeats. Importing the package can therefore publish package contents under names selected by the code using the caller's npm credentials.

AI rationale

Evidence

package.jsonautopublish.jspackage-lock.json

Decision evidence

public snapshot

AI called this Malicious at 97.0% confidence as Malware with low false-positive risk.

Evidence for block

The package declares autopublish.js as its main entry point, so importing it runs that file.
The entrypoint immediately starts publishing and repeats the operation after a delay.
Each cycle replaces the package name with a random name, writes package.json and package-lock.json, and runs npm publish.

Evidence against

The README openly describes the package as an auto-publishing script and tells users to run it explicitly.
No install lifecycle hook or credential collection was identified.

Behavioral surface

Source

ChildProcessFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 14.2 KB of source

Source & flagged code

7 flagged

autopublish.jsView file

1const fs = require('fs'); L2: const { exec } = require('child_process'); L3: ... L28: const animationInterval = setInterval(() => { L29: process.stdout.write('\r' + animation[currentFrame]); L30: currentFrame = (currentFrame + 1) % animation.length; ... L32: L33: let packageJson = fs.readFileSync('package.json'); L34: let packageData = JSON.parse(packageJson); L35: let randomString = generateRandomString(10); ... L45: L46: exec('npm publish --access public', (error, stdout, stderr) => {

Critical

Npm Publish Worm

Source mutates package metadata and republishes itself to npm.

autopublish.jsView on unpkg · L1

1Trigger-reachable chain: manifest.main -> autopublish.js L1: const fs = require('fs'); L2: const { exec } = require('child_process'); L3: ... L28: const animationInterval = setInterval(() => { L29: process.stdout.write('\r' + animation[currentFrame]); L30: currentFrame = (currentFrame + 1) % animation.length; ... L32: L33: let packageJson = fs.readFileSync('package.json'); L34: let packageData = JSON.parse(packageJson); L35: let randomString = generateRandomString(10); ... L45: L46: exec('npm publish --access public', (error, stdout, stderr) => {

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

autopublish.jsView on unpkg · L1

Findings

2 Critical6 High1 Medium3 Low

CriticalNpm Publish Wormautopublish.js

CriticalTrigger Reachable Dangerous Capabilityautopublish.js

HighChild Processautopublish.js

HighShell

HighKnown Malware Source Fingerprint Signatureautopublish3.js

HighAi Review Evidencepackage.json

HighAi Review Evidenceautopublish.js

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to pure_opossum_amaranth-54@2.3.2.

The versions list below shows the verdict for each recorded version.

Avoid installing pure_opossum_amaranth-54@2.3.2. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-11-04 09:52:33.132Z (UTC).

Source advisory published: 2026-11-02 09:44:21.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

2.3.2latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 4:23 PM

registry / Malware / pure_opossum_amaranth-54

pure_opossum_amaranth-54

This report shows the evidence for pure_opossum_amaranth-54@2.3.2, the only known version.

AI Security Review

scanned 13h ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review

Trigger

Import of the package through its main entrypoint; the README also documents direct script execution.

Impact

May publish package contents repeatedly to npm under names chosen by the script, using the caller's npm authentication and current-directory files.

Mechanism

The entrypoint edits package metadata and invokes npm publish, then schedules another cycle.

Attack narrative

AI rationale

Evidence

package.jsonautopublish.jspackage-lock.json

Decision evidence

public snapshot

AI called this Malicious at 97.0% confidence as Malware with low false-positive risk.

Evidence for block

The package declares autopublish.js as its main entry point, so importing it runs that file.
The entrypoint immediately starts publishing and repeats the operation after a delay.
Each cycle replaces the package name with a random name, writes package.json and package-lock.json, and runs npm publish.

Evidence against

The README openly describes the package as an auto-publishing script and tells users to run it explicitly.
No install lifecycle hook or credential collection was identified.

Behavioral surface

Source

ChildProcessFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 14.2 KB of source

Source & flagged code

7 flagged

autopublish.jsView file

Critical

Npm Publish Worm

Source mutates package metadata and republishes itself to npm.

autopublish.jsView on unpkg · L1

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

autopublish.jsView on unpkg · L1

Findings

2 Critical6 High1 Medium3 Low

CriticalNpm Publish Wormautopublish.js

CriticalTrigger Reachable Dangerous Capabilityautopublish.js

HighChild Processautopublish.js

HighShell

HighKnown Malware Source Fingerprint Signatureautopublish3.js

HighAi Review Evidencepackage.json

HighAi Review Evidenceautopublish.js

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to pure_opossum_amaranth-54@2.3.2.

The versions list below shows the verdict for each recorded version.

Avoid installing pure_opossum_amaranth-54@2.3.2. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-11-04 09:52:33.132Z (UTC).

Source advisory published: 2026-11-02 09:44:21.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

2.3.2latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 4:23 PM

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Related packages

Other malware packages