Skip to navigation

Threat reportSupply ChainTL-2026-1491

"Download Pumping" — npm Supply-Chain Trust-Signal Abuse via Mass Version Uploads (ambar-src / reverse_ssh / Apfell)

highACTIVE

Tenable researcher Ron Popov documented 'download pumping', a supply-chain deception technique in which attackers publish hundreds of package versions in rapid succession so that registry mirrors, security scanners, and analysis bots auto-download each release, artificially inflating download counts and version-history depth to fake legitimacy.

Key facts

IdentifiersTL-2026-1491
Also known asDownload Pumping, ambar-src campaign
SeverityHIGH
Affected productsnpm, Inc. / npm public registry npm package registry (registry.npmjs.org) and dependent automated infrastructure (mirrors, security scanners, analysis bots); npm ecosystem ambar-src (malicious npm package, typosquat of ember-source); Multiple package-registry operators PyPI, RubyGems, NuGet (registries described by researchers as architecturally comparable/similarly exposed; no confirmed exploitation reported)
Weaknesses (CWE)CWE-506, CWE-1357, CWE-829
MalwareApfell, reverse_ssh
ToolsMythicAgents / Mythic C2
MITRE ATT&CK techniquesT1005 Data from Local System, T1027 Obfuscated Files or Information, T1056 Input Capture, T1059 Command and Scripting Interpreter, T1071 Application Layer Protocol, T1082 System Information Discovery, T1102 Web Service, T1105 Ingress Tool Transfer, T1113 Screen Capture, T1140 Deobfuscate/Decode Files or Information, T1195 Supply Chain Compromise, T1204 User Execution and 9 more in the attack flow
MotivationUNKNOWN
Target sectorstechnology, software-development, government administration, finance, health
Target regionsGlobal
Detection rules9 (1 shown free)
Sources10 cited sources

Detection coverage

As of 2026-07-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1491 across Splunk SPL, Microsoft KQL and Sigma, covering 18 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: npm Preinstall/Postinstall Lifecycle Script Spawning Encoded Interpreter (ambar-src Exploitation)

Detects npm/node/yarn spawning powershell.exe or cmd.exe with encoded/hex-decode command-line arguments immediately following a package install, matching the ambar-src preinstall lifecycle-script abuse pattern that triggers with no explicit require()/import.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1195.002, T1546.016, T1027, T1140
  • Data sources: sysmon, windows_security, endpoint_edr
  • Severity: critical
  • Confidence: high

Splunk SPL

index=endpoint sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| search (ParentImage="*\\node.exe" OR ParentImage="*\\npm.cmd" OR ParentImage="*\\npm.exe" OR ParentImage="*\\yarn.cmd")
| search (Image="*\\powershell.exe" OR Image="*\\cmd.exe")
| search (CommandLine="*-EncodedCommand*" OR CommandLine="*-enc *" OR CommandLine="*FromHexString*" OR CommandLine="*[convert]::ToInt32*")
| eval risk="high"
| table _time, ComputerName, User, ParentImage, Image, CommandLine, risk
| sort -_time

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ ("node.exe", "npm.cmd", "npm.exe", "yarn.cmd")
| where FileName in~ ("powershell.exe", "cmd.exe")
| where ProcessCommandLine has_any ("-EncodedCommand", "-enc ", "FromHexString", "ToInt32")
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine
| order by Timestamp desc

Sigma

title: npm Lifecycle Script Spawning Encoded Interpreter Command (ambar-src-style)
id: 8f2c1a40-1491-4a01-9c11-tl2026149101
status: experimental
description: Detects npm/node/yarn spawning an interpreter with encoded/hex-decode command-line arguments, matching the ambar-src preinstall lifecycle-script abuse chain.
references:
  - https://www.tenable.com/blog/how-cyberattackers-inflate-malicious-package-npm-download-counts
author: Threadlinqs Team
date: 2026-07-18
tags:
  - attack.initial_access
  - attack.execution
  - attack.t1195.002
  - attack.t1546.016
  - attack.t1027
  - attack.t1140
  - attack.tool.ambar_src
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|endswith:
      - '\node.exe'
      - '\npm.cmd'
      - '\npm.exe'
      - '\yarn.cmd'
  selection_child:
    Image|endswith:
      - '\powershell.exe'
      - '\cmd.exe'
  selection_encoded:
    CommandLine|contains:
      - '-EncodedCommand'
      - '-enc '
      - 'FromHexString'
  condition: selection_parent and selection_child and selection_encoded
falsepositives:
  - Legitimate build tooling that shells out to PowerShell for signing/packaging with base64 arguments
level: high

Known false positives:

  • Legitimate CI/CD build scripts that invoke PowerShell with base64-encoded commands for signing or artifact packaging

Tuning notes: Allowlist known internal build-agent hashes/paths that legitimately invoke encoded PowerShell; correlate with a recent `npm install`/lockfile change event to reduce noise.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • npm/node Spawning Shell Fetching from Non-Registry Domain — Linux Exploitation Chain · unlock with TL Creds
  • osascript Invoked with Obfuscated Inline Script on macOS Build/Dev Hosts (Post-Exploitation) · unlock with TL Creds
  • Chrome Credential/Session Data Access Following Suspicious osascript/Node Execution (C2/Impact) · unlock with TL Creds
  • Burst npm Package Version Publish Rate (Download-Pumping / Trust-Signal Inflation) · unlock with TL Creds
  • Newly Published Package Version Installed Into CI/CD Within Minutes of Publish (Minimum-Age Gate Bypass) · unlock with TL Creds
  • reverse_ssh-style Reverse Shell Callback Pattern from Linux Build Host (C2/Lateral Movement) · unlock with TL Creds
  • Post-Install Drop of Unsigned Loader/Backdoor Artifact After npm Install (Post-Exploitation) · unlock with TL Creds
  • Outbound Beacon to Yandex Cloud Functions / [indicator] C2 Relay from Dev or Build Host (C2) · unlock with TL Creds

Indicators of compromise

As of 2026-07-18, Threadlinqs Intelligence tracks 18 indicators of compromise for TL-2026-1491.

Sample indicators (3 of 18)

  • Domain: x-ya[.]ru
  • URL: hxxps://functions[.]yandexcloud[.]net/d4eblscvbp200glhmmcoePl
  • File hash: 9b76e275d989ebc3b43911a5e1d2b64ef9544a6b1dbc69a3412bd0ccadaed567

Defanged, TLP:CLEAR. Full set of 18 indicators: unlock with TL Creds.

18 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

The technique was proven in the wild via the malicious npm package 'ambar-src' (a typosquat of 'ember-source'), which reached 724 versions (428 in its first two hours) and ~50,000 downloads in three days before npm removed it, then dropped platform-specific malware (Windows: encrypted-shellcode loader; Linux: reverse_ssh; macOS: Apfell/MythicAgents) via a hex-encoded preinstall script.

In mid-February 2026 Tenable Research identified a malicious npm package, 'ambar-src', that typosquatted the popular 'ember-source' package (11M+ downloads). The package was first uploaded on 2026-02-13 and published as a series of benign-looking versions — 428 of them in the first two hours alone, eventually reaching 724 total versions — before a weaponized version was pushed on 2026-02-16 at 12:18:45 UTC. npm removed the package roughly 4h44m later (17:02:44 UTC the same day), but by then it had accumulated approximately 50,000 downloads with zero legitimate human users.

The malicious version abused npm's `preinstall` lifecycle script hook defined in package.json: merely running `npm install ambar-src`, or having it resolve transitively as a dependency, was sufficient to trigger the payload with no explicit `require()`/import needed. The `index.js` preinstall script executed a hex-encoded, OS-specific one-liner to obscure intent, and the package interspersed legitimate-looking utility code (MathUtils, StringUtils, time helpers) with the malicious logic to evade cursory review.

Platform-specific second-stage payloads were fetched from the attacker-controlled domain x-ya[.]ru: on Windows, an encrypted-shellcode loader (msinit.exe, ~400KB) decoded and executed the shellcode in memory; on Linux, a bash script pulled an ELF binary ('osa') identified via Golang build metadata as a variant of the open-source reverse_ssh backdoor; on macOS, a nohup-wrapped hex command invoked the native `osascript` utility to run a ~500KB JavaScript payload identified as Apfell, part of the MythicAgents C2 framework family, capable of reconnaissance, screenshot capture, Google Chrome credential/session data theft, and fake password-prompt phishing overlays. Command-and-control communications were relayed through Yandex Cloud Functions (function.yandexcloud[.]ru / functions.yandexcloud.net), abusing a well-known cloud service to blend in with legitimate traffic (MITRE T1102 Web Service).

Separately, and more broadly, Tenable's Ron Popov demonstrated the underlying 'download pumping' abuse pattern with proof-of-concept test packages: every new version publish triggers automated downloads from registry mirrors and security-scanner/analysis-bot infrastructure — 135.55 downloads/version for a plain version bump, 141.91 for a static postinstall script, and 158.16 for a dynamically-changing postinstall script, implying scanners preferentially re-fetch versions that look newly suspicious. Because scanners can often determine whether a postinstall script exists purely from package metadata (without downloading the tarball), attackers can game detection infrastructure itself into serving as an amplification network. Tenable also revalidated a 2021-era technique of direct tarball-URL HTTP request flooding, inflating a test package to 17,000 downloads in about one hour — showing the older method still works alongside the newer one. ReversingLabs' write-up (crediting Popov) and Tenable's own technical FAQ both note the underlying registry infrastructure pattern is not npm-specific: PyPI, RubyGems, and NuGet operate comparable automated-mirror/scanner ecosystems and are described as similarly exposed.

The attack is notable for its convergence with AI-assisted coding tools, which frequently use download counts, version-history density, and maintenance-activity signals as heuristics for package trustworthiness/recommendation — none of which were designed as security controls and all of which download pumping can fabricate cheaply. Recommended mitigations center on enforcing minimum package-age windows (3-4+ days) before a newly published version is eligible for use in CI/CD or production, alongside version pinning, least-privilege network egress for build/CI environments, ephemeral just-in-time credentials in place of long-lived tokens, and stronger maintainer/publish authentication. Dissenting industry voices (James Shank, Expel; John Strand, BHIS) argued minimum-age gates only delay rather than prevent the attack, and that delaying legitimate updates may itself introduce operational risk that outweighs the benefit in many organizations.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System; T1113 Screen Capture

Defense Evasion

T1027 Obfuscated Files or Information; T1140 Deobfuscate/Decode Files or Information; T1218 System Binary Proxy Execution; T1620 Reflective Code Loading

Credential Access

T1056 Input Capture; T1555 Credentials from Password Stores

Execution

T1059 Command and Scripting Interpreter; T1204 User Execution

Command and Control

T1071 Application Layer Protocol; T1102 Web Service; T1105 Ingress Tool Transfer

Discovery

T1082 System Information Discovery

Initial Access

T1195 Supply Chain Compromise

Impact

T1491 Defacement

Persistence

T1505 Server Software Component; T1546 Event Triggered Execution

Resource Development

T1584 Compromise Infrastructure; T1585 Establish Accounts; T1587 Develop Capabilities

Remediation

Patches

  • No vendor patch applicable — 'ambar-src' was removed from the npm registry by npm within ~4h44m of the malicious version's publication (2026-02-16 12:18:45 UTC to 17:02:44 UTC)

Immediate actions

  • Treat any host that ran `npm install ambar-src` (or resolved it transitively) as fully compromised; do not attempt in-place cleanup
  • Rotate all secrets, API keys, tokens, and credentials stored on or accessible from an affected host, performed from a separate, known-clean machine
  • Block outbound connections to x-ya[.]ru, function.yandexcloud[.]ru, and the identified functions.yandexcloud.net URL paths
  • Search EDR/process telemetry for msinit.exe, the ELF binary 'osa', reverse_ssh process indicators, and osascript spawning unexpected child processes or network connections
  • Audit npm lockfiles and CI/CD dependency trees for 'ambar-src' or any package with an unexplained sudden spike (100s) of version publishes in a short window

Workarounds

  • Configure npm/yarn/pnpm to respect a package minimum-age threshold where supported before allowing install of newly published versions
  • Use internal registry proxies/mirrors with allowlisting so newly published packages require manual/automated security review before becoming installable org-wide

Longer-term hardening

  • Enforce a minimum package-age gate (3-4+ days) before a newly published registry version is permitted in CI/CD or production builds
  • Adopt version pinning / lockfile-only installs and disable automatic minor/patch version resolution in build pipelines
  • Replace long-lived npm/CI publish and consumption tokens with ephemeral, just-in-time scoped credentials
  • Apply least-privilege egress network policy to CI/CD runners and developer build environments to limit preinstall/postinstall script network access
  • Do not use raw download counts, version-history density, or publish-frequency as trust/legitimacy signals in internal tooling or AI-assisted package recommendation logic
  • Strengthen maintainer account authentication (mandatory 2FA/WebAuthn) on registry publish accounts

Affected and fixed versions

  • npm, Inc. / npm public registry — npm package registry (registry.npmjs.org) and dependent automated infrastructure (mirrors, security scanners, analysis bots)
    Vulnerable versions: all versions of npm registry lifecycle-script/version-publish infrastructure as of 2026-02
  • npm ecosystem — ambar-src (malicious npm package, typosquat of ember-source)
    Vulnerable versions: 1 through 724 (malicious payload introduced in the version published 2026-02-16 12:18:45 UTC)
    Fixed in: removed from registry entirely 2026-02-16 17:02:44 UTC
  • Multiple package-registry operators — PyPI, RubyGems, NuGet (registries described by researchers as architecturally comparable/similarly exposed; no confirmed exploitation reported)
    Vulnerable versions: automated mirror/scanner infrastructure generally

Timeline

  • Independent researcher publicly demonstrates direct tarball-URL HTTP request flooding to spoof npm download counts, generating roughly 1 million spoofed downloads weekly — the precursor abuse pattern Tenable later revalidated
  • Cybernews, Security Boulevard, DevOps.com, and other outlets report on the ambar-src incident and its 50,000-download compromise
  • Tenable publishes its technical FAQ/analysis on the ambar-src malicious package, detailing platform-specific payloads, hashes, and C2 infrastructure
  • The 'ambar-src' package (typosquatting 'ember-source') is first published to the npm registry; 428 benign-looking versions are uploaded within the first two hours
  • By the time of removal and continuing to be tallied over the following days, ambar-src reaches 724 total published versions and approximately 50,000 downloads with zero legitimate users
  • npm removes ambar-src from the public registry at 17:02:44 UTC, roughly 4 hours 44 minutes after the malicious version's publication
  • A weaponized version of ambar-src is published at 12:18:45 UTC, containing a hex-encoded preinstall script that fetches OS-specific payloads from locked-ioc-12
  • Tenable researcher Ron Popov publishes the broader 'download pumping' research, generalizing the ambar-src version-flooding pattern into a named technique and publishing proof-of-concept download-amplification measurements
  • ReversingLabs publishes 'Download pumping joins the trust-abuse bandwagon', crediting Tenable/Popov, summarizing the technique for a broader audience and noting industry pushback on minimum-age mitigations from James Shank (Expel) and John Strand (BHIS)

Sources cited

Previous and next in supply chain

Further reading

Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats