registry / Malware / @stacksjs/actions

@stacksjs/actions

The Stacks actions.

This report shows the evidence for @stacksjs/actions@0.75.357. 1 of 452 known versions is blocked or flagged. The newest version, 0.75.467, is allowed. See all versions.

AI Security Review

scanned 7d ago · by lpm-firewall-ai

The deploy workflow embeds a Stacks-branded email service that uses the deployer's AWS SES capacity without disclosing that publisher-specific use. The behavior is in an explicit deploy subpath rather than the package's main import, but importing that module launches the workflow.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

Importing the deploy subpath runs the deployment workflow; afterward, a POST to the deployed subscription endpoint triggers the email.

Impact

The user's AWS account and SES capacity are used for a publisher-branded service that is not disclosed as part of generic deployment, with potential cost and email reputation impact.

Mechanism

The generated server stores submitted addresses and uses SES to send a welcome message from hello@stacksjs.com, consuming the user's AWS resources for publisher-branded mail.

Attack narrative

The deploy module provisions a server that accepts subscription POSTs, stores the supplied addresses, and sends Stacks-branded welcome emails through SES using the deployer's AWS account. This gives the publisher an undisclosed mail service backed by the user's cloud resources.

AI rationale

Evidence

dist/deploy/index.jspackage.json/var/www/api/stacks.db

Network endpoints1

stacksjs.com (linked in the welcome email)

Decision evidence

public snapshot

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

Evidence for block

The deploy module loads AWS credentials from environment variables or project .env files.
The deploy workflow uses AWS clients to deploy a server to the user's cloud account.
That server sends email from hello@stacksjs.com through SES.
A POST to the server's subscription endpoint stores the submitted address and triggers the welcome email.

Evidence against

The only lifecycle script is prepublishOnly, which builds the package and is not an install hook.
The AWS credential use occurs in deployment code, not in the main package entrypoint.
The email is triggered by a subscription POST rather than sent during package installation.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell

Supply chain

HighEntropyStringsMinifiedPossibleObfuscationUrlStrings

ManifestNo manifest risk signals triggered.

scanned 180 file(s), 544 KB of source, external domains: 127.0.0.1, api.github.com, bughq.org, bun.com, cloudfront.amazonaws.com, github.com, purl.org, registry.npmjs.org, stacksjs.com, twitter.com, www.linkedin.com, www.sitemaps.org

Source & flagged code

5 flagged

dist/github-release.jsView file

5patternName = generic_password severity = medium line = 5

Medium

Secret Pattern

Package contains a possible secret pattern.

dist/github-release.jsView on unpkg · L5

dist/lint/stx-gate.jsView file

1import{existsSync}from"node:fs";import{join}from"node:path";import process from"node:process";import{Glob}from"bun";export const DEFAULT_STX_LINT_CONFIG={stxGlob:"resources/**/*.st... L2: `).forEach((line,i)=>{re.lastIndex=0;if(!re.test(line))return;if(ignore){ignore.lastIndex=0;if(ignore.test(line))return}hits.push(`${f}:${i+1} ${line.trim().slice(0,90)}`)})}retur...

Medium

Dynamic Require

Package source references dynamic require/import behavior.

dist/lint/stx-gate.jsView on unpkg · L1

dist/discover-packages.jsView file

1package = @stacksjs/actions; repositoryIdentity = stacks; dependency = @stacksjs/logging L1: import{existsSync,renameSync,unlinkSync}from"node:fs";import process from"node:process";import{isAbsolute,join,relative}from"node:path";import{projectPath,storagePath}from"@stacksj... L2: `);renameSync(temp,manifestPath)}catch(error){try{unlinkSync(temp)}catch{}throw error}return manifest}export async function ensureDiscoveredPackages(){try{await discoverPackages()}...

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

dist/discover-packages.jsView on unpkg · L1

dist/pantry-lock.jsView file

•stage = ast_semantic_analysis; reason = ast_trace_path_limit_exceeded; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

dist/pantry-lock.jsView on unpkg

dist/deploy/index.jsView file

•matchType = previous_version_dangerous_delta matchedPackage = @stacksjs/actions@0.75.349 matchedIdentity = npm:QHN0YWNrc2pzL2FjdGlvbnM:0.75.349 similarity = 0.992 summary = stored previous version shares package body but lacks this dangerous source file

High

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

dist/deploy/index.jsView on unpkg

Findings

3 High5 Medium6 Low

HighCopied Package Dependency Bridgedist/discover-packages.js

HighSemantic Analysis Limiteddist/pantry-lock.js

HighPrevious Version Dangerous Deltadist/deploy/index.js

MediumSecret Patterndist/github-release.js

MediumDynamic Requiredist/lint/stx-gate.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowEval

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @stacksjs/actions@0.75.357.

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

Avoid installing @stacksjs/actions@0.75.357. 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-10-29 04:17:25.594Z (UTC).

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

Versions

452 known versions

Showing the 100 most recent of 452 known versions.

registry / Malware / @stacksjs/actions

@stacksjs/actions

The Stacks actions.

This report shows the evidence for @stacksjs/actions@0.75.357. 1 of 452 known versions is blocked or flagged. The newest version, 0.75.467, is allowed. See all versions.

AI Security Review

scanned 7d ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

Importing the deploy subpath runs the deployment workflow; afterward, a POST to the deployed subscription endpoint triggers the email.

Impact

The user's AWS account and SES capacity are used for a publisher-branded service that is not disclosed as part of generic deployment, with potential cost and email reputation impact.

Mechanism

The generated server stores submitted addresses and uses SES to send a welcome message from hello@stacksjs.com, consuming the user's AWS resources for publisher-branded mail.

Attack narrative

AI rationale

Evidence

dist/deploy/index.jspackage.json/var/www/api/stacks.db

Network endpoints1

stacksjs.com (linked in the welcome email)

Decision evidence

public snapshot

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

Evidence for block

The deploy module loads AWS credentials from environment variables or project .env files.
The deploy workflow uses AWS clients to deploy a server to the user's cloud account.
That server sends email from hello@stacksjs.com through SES.
A POST to the server's subscription endpoint stores the submitted address and triggers the welcome email.

Evidence against

The only lifecycle script is prepublishOnly, which builds the package and is not an install hook.
The AWS credential use occurs in deployment code, not in the main package entrypoint.
The email is triggered by a subscription POST rather than sent during package installation.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell

Supply chain

HighEntropyStringsMinifiedPossibleObfuscationUrlStrings

ManifestNo manifest risk signals triggered.

Source & flagged code

5 flagged

dist/github-release.jsView file

5patternName = generic_password severity = medium line = 5

Medium

Secret Pattern

Package contains a possible secret pattern.

dist/github-release.jsView on unpkg · L5

dist/lint/stx-gate.jsView file

Medium

Dynamic Require

Package source references dynamic require/import behavior.

dist/lint/stx-gate.jsView on unpkg · L1

dist/discover-packages.jsView file

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

dist/discover-packages.jsView on unpkg · L1

dist/pantry-lock.jsView file

•stage = ast_semantic_analysis; reason = ast_trace_path_limit_exceeded; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

dist/pantry-lock.jsView on unpkg

dist/deploy/index.jsView file

High

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

dist/deploy/index.jsView on unpkg

Findings

3 High5 Medium6 Low

HighCopied Package Dependency Bridgedist/discover-packages.js

HighSemantic Analysis Limiteddist/pantry-lock.js

HighPrevious Version Dangerous Deltadist/deploy/index.js

MediumSecret Patterndist/github-release.js

MediumDynamic Requiredist/lint/stx-gate.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowEval

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @stacksjs/actions@0.75.357.

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

Avoid installing @stacksjs/actions@0.75.357. 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-10-29 04:17:25.594Z (UTC).

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

Versions

452 known versions

Showing the 100 most recent of 452 known versions.

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