SShortSingh.
Back to feed

Malicious npm Package Used Ethereum Smart Contract to Hide C2 Infrastructure

0
·79 views

Security firm Checkmarx discovered that a malicious npm package called indexed-btree, mimicking the legitimate sorted-btree library, had accumulated nearly 2 million weekly downloads before being identified as malware. Unlike typical supply chain attacks, the package contained no install scripts, instead hiding its loader inside a standard library method that triggered only when called with a specific argument. Once activated, the malware collected system details such as hostname, CPU, and memory, then transmitted them to hardcoded Slack and Telegram channels. It used a smart contract on the Ethereum Sepolia testnet to dynamically retrieve its command-and-control server address, making it resilient to domain or IP blocking. The malware also fetched an encrypted second-stage payload via the same smart contract using X25519 key exchange and AES decryption, though the contents of that payload have not been publicly disclosed.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Auditing Terraform for Cloud Lock-In Before Migrating to a European Provider

Engineers planning a move off a hyperscaler can scan their Terraform files and state to find lock-in before migrating. Resources should be sorted into three tiers: standard portable components such as VMs, PostgreSQL, and S3-compatible storage; managed services needing config changes; and proprietary services like DynamoDB or BigQuery that force application code rewrites. The audit should also cover application dependencies, since a resource only creates real lock-in when code calls its proprietary SDK directly rather than a standard protocol. The article notes that Terraform standardizes provisioning syntax but does not make infrastructure portable, because each provider uses distinct resource names and APIs. Teams are advised to run scanners in CI/CD pull requests to prevent new proprietary dependencies while planning the migration.

0
ProgrammingDEV Community ·

Seven Proxy Providers Compared for Web Scraping and Automation Developers

A DEV Community post from Dev Stack Hub reviews seven leading proxy providers for developers working on web scraping and automation. The article compares the providers' features to help readers identify which option suits their development needs. It is positioned as a discussion piece tagged around web scraping and Python. The post was published on November 8 and runs about 12 minutes to read. The available text does not detail the specific providers or their individual findings.

0
ProgrammingDEV Community ·

n8n Tops Nine-Tool Comparison of AI Workflow Automation Platforms for 2027

A new comparison evaluates nine AI workflow automation tools, which link business apps and insert AI models into the steps between them. The assessment scores each tool on eight criteria, split between reliability (output validation, failure handling, run visibility) and governance (identity, policy, audit trail, change control, hosting and data controls). n8n ranks first overall, with the highest reliability score at 89%, and suits teams that want to self-host and choose their own model. Barndoor Automations and UiPath tie for second place with identical overall scores of 66.7, while the remaining six tools fall within 3.3 points of one another. The author cautions against reading closely into the order of the lower-ranked tools given how narrow the gaps are.

0
ProgrammingDEV Community ·

Seven Pitfalls That Distort Latency Arbitrage Measurements, and How to Check for Them

Measuring how long a broker's quote lags behind a faster price feed appears simple but is easily skewed by the measurement method itself. The author, testing XAUUSD quotes at three retail brokers, compiled a checklist of common traps that make stale-quote windows seem more frequent, longer, or more profitable than they are. Key issues include clock drift between separately timestamped feeds, one-second snapshots that erase sub-second windows, and comparing mid prices instead of the tradable cross-side spread. A second fast feed showed more windows per hour but also many crossed or zero-spread quotes, so its extra windows were mostly noise. Each pitfall is paired with a concrete check the reader can run on their own data.