Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@smithy/signature-v4
Advanced tools
A standalone implementation of the AWS Signature V4 request signing algorithm
@smithy/signature-v4 is an npm package used for signing AWS requests using the AWS Signature Version 4 signing process. This is essential for securely making authenticated requests to AWS services.
Signing HTTP Requests
This feature allows you to sign HTTP requests to AWS services using the AWS Signature Version 4 signing process. The code sample demonstrates how to sign a GET request to an S3 bucket.
const { SignatureV4 } = require('@smithy/signature-v4');
const { Sha256 } = require('@aws-crypto/sha256-js');
const { HttpRequest } = require('@smithy/protocol-http');
const signer = new SignatureV4({
service: 's3',
region: 'us-east-1',
credentials: {
accessKeyId: 'AKID',
secretAccessKey: 'SECRET'
},
sha256: Sha256
});
const request = new HttpRequest({
method: 'GET',
hostname: 'examplebucket.s3.amazonaws.com',
path: '/exampleobject'
});
signer.sign(request).then(signedRequest => {
console.log(signedRequest);
});
Presigning URLs
This feature allows you to generate presigned URLs for AWS services, which can be used to grant temporary access to resources. The code sample demonstrates how to presign a URL for an S3 object with a 1-hour expiration.
const { SignatureV4 } = require('@smithy/signature-v4');
const { Sha256 } = require('@aws-crypto/sha256-js');
const { HttpRequest } = require('@smithy/protocol-http');
const { formatUrl } = require('@smithy/util-format-url');
const signer = new SignatureV4({
service: 's3',
region: 'us-east-1',
credentials: {
accessKeyId: 'AKID',
secretAccessKey: 'SECRET'
},
sha256: Sha256
});
const request = new HttpRequest({
method: 'GET',
hostname: 'examplebucket.s3.amazonaws.com',
path: '/exampleobject'
});
signer.presign(request, { expiresIn: 3600 }).then(presignedUrl => {
console.log(formatUrl(presignedUrl));
});
The aws-sdk package is the official AWS SDK for JavaScript, which includes a wide range of functionalities for interacting with AWS services, including request signing. It provides a higher-level abstraction compared to @smithy/signature-v4, making it easier to use for common tasks but less flexible for custom signing needs.
The aws4 package is a lightweight library for signing AWS requests with AWS Signature Version 4. It is similar to @smithy/signature-v4 in that it focuses specifically on request signing, but it is less integrated with the broader AWS SDK ecosystem.
This package contains an implementation of the AWS Signature Version 4 authentication scheme.
It is internal to Smithy-TypeScript generated clients, and not generally intended for standalone usage outside this context.
For custom usage, inspect the interface of the SignatureV4 class.
FAQs
A standalone implementation of the AWS Signature V4 request signing algorithm
The npm package @smithy/signature-v4 receives a total of 14,234,916 weekly downloads. As such, @smithy/signature-v4 popularity was classified as popular.
We found that @smithy/signature-v4 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.