
Research
/Security News
Intercom’s npm Package Compromised in Ongoing Mini Shai-Hulud Worm Attack
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.
For programmatically deploying an arbitrary number of pre-compiled Solidity smart contracts.
You can also clone the repo to access a clunky command line utility for, given .sol source files, finding dependencies of smart contracts and joining them into a single source file for easy Etherscan verification.
Install using npm install chain-end. Command line utilities require Python.
The imported package contains the following relevant properties:
contracts object, which contains the JSON (truffle compile output) of the default contractsDeployer class
Deployer(web3Provider, accountAddress, gasLimit)
Deployer(web3Provider, accountAddress) to let MetaMask handle transaction gasdeployer.addContract(compiledJSON)
compiledJSON must be an undeployed, compiled Truffle artifact, i.e. the output of truffle compileconst instance = deployer.deploy(contractName, constructorParameters)
contracts or the name of a contract added using addContractsrc/web3/deployer.js for additional methods you may want to usedeploy function, which exposes the internal API of Deployer for stateless deployment
deploy(contractJSON, constructorParams, web3Provider, web3Account, gasLimit)gasLimit is optionalgetInstance function, which retrieves a deployed contract given its artifact, its deployed address, a provider, and (optionally) a sender accountcallInstance function, which calls a specified function from a given TruffleContract instance and returns the resultNote: GitHub repository only, also literally the hackiest thing you've ever seen.
All scripts must be run from the chain-end project root directory.
yarn cli-setup.sol files in solidity/source_files/raw
raw/raw/dependenciesraw/ will contain all OpenZeppelin contracts in the openzeppelin-contracts folder (note the version in package.json)yarn get-metadata, notice the files output in solidity/metadatayarn join-source-files -- solidity/metadata/metadataFile solidity/metadata/filepathsFile
yarn solcompilemodule.exports.contracts
solidity/compiledsolidity/source_files/completeIf the metadata interests you, here is a partial example output:
{
"Address": {
"compiler": "^0.5.0",
"dependencies": [],
"name": "Address",
"type": "library"
},
"AllowanceCrowdsale": {
"compiler": "^0.5.0",
"dependencies": [
"Crowdsale",
"IERC20",
"Math",
"SafeERC20",
"SafeMath"
],
"name": "AllowanceCrowdsale",
"type": "contract"
},
...
}
MIT
FAQs
Programmatic pre-compiled Truffle contract deployment
The npm package chain-end receives a total of 36 weekly downloads. As such, chain-end popularity was classified as not popular.
We found that chain-end demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.

Research
Socket detected a malicious supply chain attack on PyPI package lightning versions 2.6.2 and 2.6.3, which execute credential-stealing malware on import.

Research
A brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.